* [ISSUE] Restructuring/Organizing general Packages etc.
@ 2023-12-31 22:44 removewingman
2023-12-31 22:49 ` classabbyamp
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: removewingman @ 2023-12-31 22:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
New 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
@ 2023-12-31 22:49 ` classabbyamp
2023-12-31 22:54 ` [ISSUE] [CLOSED] " removewingman
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2023-12-31 22:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873049957
Comment:
xbps-src needs all packages in the same repo for dependency resolution and other functionality
gitlab is fairly out of the question:
1. (IMO) the UI/UX are awful to the point of giving me a headache whenever I have to use it
2. the amount of compute for CI we get provided free by github would be prohibitively expensive to replace on other platforms
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ISSUE] [CLOSED] Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
2023-12-31 22:49 ` classabbyamp
@ 2023-12-31 22:54 ` removewingman
2023-12-31 22:54 ` removewingman
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: removewingman @ 2023-12-31 22:54 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc 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
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: removewingman @ 2023-12-31 22:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
New comment by removewingman on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873050466
Comment:
Thanks for the answer, I did not know that with the dependencies what a bummer.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (2 preceding siblings ...)
2023-12-31 22:54 ` removewingman
@ 2023-12-31 23:06 ` removewingman
2024-01-01 2:26 ` classabbyamp
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: removewingman @ 2023-12-31 23:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
New comment by removewingman on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873052065
Comment:
I'm curious could you not provide for each repo one file where every package is listed, and the build script has every file of each repo locks through it and searches for the dependencies, that is how the build script knows in which repo to get the dependencies from, wouldn't that solve the problem? What is the other functionality, so that everything needs to stay in one repo?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (3 preceding siblings ...)
2023-12-31 23:06 ` removewingman
@ 2024-01-01 2:26 ` classabbyamp
2024-01-01 10:09 ` removewingman
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2024-01-01 2:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873111862
Comment:
if you move things into multiple repos, you make any kind of large change (e.g. ones that require rebuilding many packages) much harder. you'd have to coordinate pull requests or pushes between repos, ensure every repo has consistent state, do git actions many times over to sync all the different repos, etc.
it's just harder to manage, and would require significant rework of infrastructure and processes.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (4 preceding siblings ...)
2024-01-01 2:26 ` classabbyamp
@ 2024-01-01 10:09 ` removewingman
2024-01-01 13:32 ` [ISSUE] [CLOSED] " Duncaen
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: removewingman @ 2024-01-01 10:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
New comment by removewingman on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873258513
Comment:
In my opinion it would be worth it, as the projects grows in the long run makes it easier. But in the end it is your decision.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ISSUE] [CLOSED] Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (5 preceding siblings ...)
2024-01-01 10:09 ` removewingman
@ 2024-01-01 13:32 ` Duncaen
2024-01-01 13:32 ` Duncaen
2024-01-01 14:41 ` [ISSUE] [CLOSED] " classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: Duncaen @ 2024-01-01 13:32 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (6 preceding siblings ...)
2024-01-01 13:32 ` [ISSUE] [CLOSED] " Duncaen
@ 2024-01-01 13:32 ` Duncaen
2024-01-01 14:41 ` [ISSUE] [CLOSED] " classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: Duncaen @ 2024-01-01 13:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873330045
Comment:
There is absolutely no way it would make anything easier to run in the long run, @classabbyamp has a more in-depth understanding of how this repository works.
Even simple packages have chains of dependencies that go into hundreds of packages, orchestrating changes through multiple git repositories is simply not feasible. Large organization use mono-repos for similar reasons, it just makes everything easier to manage and orchestrate and its not like our repository is that big either, the only big problem is the single large `srcpkgs` directory.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ISSUE] [CLOSED] Restructuring/Organizing general Packages etc.
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc removewingman
` (7 preceding siblings ...)
2024-01-01 13:32 ` Duncaen
@ 2024-01-01 14:41 ` classabbyamp
8 siblings, 0 replies; 10+ messages in thread
From: classabbyamp @ 2024-01-01 14:41 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2024-01-01 14:41 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-31 22:44 [ISSUE] Restructuring/Organizing general Packages etc 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 ` [ISSUE] [CLOSED] " Duncaen
2024-01-01 13:32 ` Duncaen
2024-01-01 14:41 ` [ISSUE] [CLOSED] " classabbyamp
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).