Looking forward to RSEL 7.1! If I understood you correctly, I like the idea of a "rolling repo", where updates to 7.0 take you to the 7.1 version. I don't believe that most updates will necessarily result in an update flood (many updates to satisfy dependencies of a single package update), but even if it did...I haven't had a problem with doing just that in my use of another prominent North American enterprise distro.
-Marc On Wed, Apr 8, 2015 at 5:37 PM, Jacco Ligthart <[email protected]> wrote: > All, > > As I hinted before, I'm busy building RSEL 7.1. > I first build all packages based on the CentOS git repository. So I've > now got a working set. I wanted to build them all twice as there are > some library version issues. So now I'm building the "official" CentOS > source rpm's against the working set. > > What I wondered though is how to distribute the resulting packages. > Ideally we should make a complete working branch, i.e. one repository > with all the updates for 7.1 merged with the older packages from 7.0. > This course of action would however take (again) quite a bit of disk > space (RSEL 7.0 alpha is around 16G) > Another option is to see them as 'just updates' and put it all in the > updates tree. > > Any other options that come to mind? any opinions? > > Of course we still need to do the "debranding" and set a course out of > the alpha stage ... > > Jacco > _______________________________________________ > users mailing list > [email protected] > http://lists.redsleeve.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
