-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repo reorg bikeshed #573
Comments
Very interested in point 3. We could remove a lot of special casing from a lot of places if we could uniformly expect the same identifiers across all targets. OpenBSD did Would is also be worth in the same change getting rid of the specialness of the |
+1 to having |
That would certainly be a way of simplifying void-linux/void-infrastructure#142 since the nginx replacement rules could just be dropped. |
I think it would still be valuable to have the redirect rules, to ensure that older installs aren't completely screwed |
related to: void-linux/void-infrastructure#142
@the-maldridge expressed interest in the new layout being
.../<XBPS_ARCH>/...
, and I think I agree that this would make the most sense.I think the best way to implement this in xbps (and having the side benefit of preventing needing to
-R
other arch's repos when installing something for anotherXBPS_ARCH
) would be to allow templating repo urls:repository=https://repo-default.voidlinux.org/current/{{XBPS_ARCH}}/
{{XBPS_ARCH}}
,%XBPS_ARCH%
were thoughts I had.ARCH
andLIBC
?<arch>
-><arch>-glibc
?<arch>
would have to stick around as a legacy alias of course.I am interested in implementing this once some of the details are hashed out
The text was updated successfully, but these errors were encountered: