Open classabbyamp opened 1 year ago
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 %p
for a long time iirc for their equivalent of this feature. Maybe something similar with a shorter component?
Would is also be worth in the same change getting rid of the specialness of the main
repository and putting it into its own directory? I think it would be nicer that way since it means you can have more selective rsync, but it also makes it much more complicated for downstream repos to gracefully cut over. This may just be a change we have to have a flag day for.
+1 to having .../<xbps_arch>/main
, but that shouldn't need anything in xbps (except default config files). aside from rsync implications, it would probably make browsing the repo manually more sane (no "too many files" message or something)
This may just be a change we have to have a flag day for.
That would certainly be a way of simplifying https://github.com/void-linux/void-infrastructure/pull/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: https://github.com/void-linux/void-infrastructure/pull/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:{{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