On 2016-01-31 23:03, Jacco Ligthart wrote:
As some of you noticed, Redsleeve 6 is getting a bit behind with
updates.
A while ago I made a complete set called 6.7. The idea was to drop some
old-and-not-used-anymore packages and create a complete set, in line
with the latest from upstream. This has not made it into a release yet,
the last show stopper is us not being able to build the latest firefox
for it.
Question: what shall I do with the updates? create an update tree next
to the current 6.7 or fold them into the current 6.7 tree, as it is
still unreleased?
If 6.7 base really is just 6.7 upstream release base, keep the updates
separate. If what we have tagged as 6.7 is 6.7 plus some updates anyway,
just fold the updates in, and deduplicate packages (only keep the latest
version if the latest version works).
It would be nice to reduce all of EL6 to just one deduplicated
repository
and archive off the rest.
(it might take a couple of days before all is build. It is now happily
building libreoffice :) )
Yeah, that takes a day or two even with decent hardware.
Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
