From: xanadu3 <xanadu3@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] XDEB .deb to .xbps converter
Date: Mon, 07 Dec 2020 01:41:31 +0100 [thread overview]
Message-ID: <20201207004131.Z2PGdGoTrMcbc6wBa-sr7p5zkvm7JH4igHM3JNP3QKE@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: 1019 bytes --]
New comment by xanadu3 on void-packages repository
https://github.com/void-linux/void-packages/issues/26981#issuecomment-739599155
Comment:
@lane-brain and @jrigg – I agree that a conversion without an adaptation of the folder structure and other distro specific details is not a good idea. I tried XDEB also with steam and in this case the autoconverted package broke my system. :D
It would be great if XDEB could be the starting point of a toolkit for the (semi) automatic creation of template files. Void is very charming on the desktop and even if "proprietary software isn't void's focus", it is often quite hard to live without it. Arch solved the problem with the toolchain around AUR, the PKGBUILD files and makepkg. In my opinion, it would be great if Void had something similar: A repository of template files, integrated into OctoXBPS.
(BTW: The ProtonMail Bridge e.g. is distributed in three formats: DEB, RPM and PKGBUILD. Wouldn't it be marvellous if they provided also an XBPS template file?)
next prev parent reply other threads:[~2020-12-07 0:41 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 [this message]
2020-12-07 2:05 ` hippi777
2020-12-07 2:08 ` hippi777
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=20201207004131.Z2PGdGoTrMcbc6wBa-sr7p5zkvm7JH4igHM3JNP3QKE@z \
--to=xanadu3@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).