From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] XDEB .deb to .xbps converter
Date: Mon, 07 Dec 2020 03:08:02 +0100 [thread overview]
Message-ID: <20201207020802.4ePBlgHf0cKm5oNG0e22YpbKtJLqA_hMcHnOcyWP9C0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26981@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
New comment by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/issues/26981#issuecomment-739619375
Comment:
hi folks! :)
i saw other distros' package managers in void, i see them as they are nice-to-have toys for making void a swiss army knife when it comes to hack on broken systems or for experimenting with whatever weird ideas and what not... :D i feel the same about xdeb! it can be used to experiment around debian stuffs while i guess xbps will track the files of the packages created by xdeb, and that renders it less of a dirty work.
other than this to my campaign for it, i guess its basically a matter of 1-2 lines inside the docs, that it exists, it is related to void, and therefore included for quick-and-dirty hacking purposes, however it is discouraged, and basically a package request is the way to go.
also, i think it should be improved, it has active maintenance, u can address the maintainer of it with requests, that is the option for creating an initial/"good enough" template, and it should get a way to prefix the path, and then it can install things under /usr/local or home, or even a chroot test environment! :)
(dont forget to) have fun on hacking! ;) (... i mean in general, and just to keep the right spirit! :D )
next prev parent reply other threads:[~2020-12-07 2:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 8:42 [ISSUE] " xanadu3
2020-12-06 13:17 ` Duncaen
2020-12-06 16:06 ` nativepapaya
2020-12-06 17:21 ` xanadu3
2020-12-06 18:22 ` nativepapaya
2020-12-06 20:45 ` jrigg
2020-12-06 20:47 ` jrigg
2020-12-06 21:20 ` xanadu3
2020-12-06 21:24 ` lane-brain
2020-12-06 21:24 ` lane-brain
2020-12-06 22:29 ` jrigg
2020-12-07 0:41 ` xanadu3
2020-12-07 2:05 ` hippi777
2020-12-07 2:08 ` hippi777 [this message]
2021-01-01 16:19 ` glaulher
2021-01-21 17:39 ` ericonr
2021-01-21 17:39 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201207020802.4ePBlgHf0cKm5oNG0e22YpbKtJLqA_hMcHnOcyWP9C0@z \
--to=hippi777@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).