From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Restructuring/Organizing general Packages etc.
Date: Mon, 01 Jan 2024 14:32:26 +0100 [thread overview]
Message-ID: <20240101133226.JyXsL6-S4kdwHYCzzyRHdDbCQbWC18AwZA_PiUnF5pA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48014@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Closed issue by removewingman on void-packages repository
https://github.com/void-linux/void-packages/issues/48014
Description:
Hello everyone,
in my opinion this repo is way to big and I would like a restructuring. My idea is to do for each category a seperate Repo. As far as my understanding goes it would be relatively easy to add more repositories to xbps. For categories there could be e.g. one for desktop environments, window managers, terminal emulators, wayland, xorg, dev-utils and so much more. The advantages are, because of the organization it is way easier to maintain and to orientate. The only problem that came to my mind is that the xbps-src script needs to be the same in all those repos, but im sure there is a solution to this problem.
The second idea I had was to switch to Gitlab instead of Github because of the group feature in Gitlab you can even better organize your Repos.
Let me know what you think of the idea.
next prev parent reply other threads:[~2024-01-01 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 22:44 [ISSUE] " removewingman
2023-12-31 22:49 ` classabbyamp
2023-12-31 22:54 ` [ISSUE] [CLOSED] " removewingman
2023-12-31 22:54 ` removewingman
2023-12-31 23:06 ` removewingman
2024-01-01 2:26 ` classabbyamp
2024-01-01 10:09 ` removewingman
2024-01-01 13:32 ` Duncaen [this message]
2024-01-01 13:32 ` Duncaen
2024-01-01 14:41 ` [ISSUE] [CLOSED] " classabbyamp
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=20240101133226.JyXsL6-S4kdwHYCzzyRHdDbCQbWC18AwZA_PiUnF5pA@z \
--to=duncaen@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).