Long time EL user/sys admin here (though historically I don't do much
packaging).  Is the disk space your biggest concern with doing it this
way?  Just from my humble point of view, I'd think that having separate
branches vs "just updates" won't show much difference in the beginning (yum
update should work effectively identically either way), but as time goes
on, provided you intend to keep moving up the version tree, it may make it
harder (and/or more messy) in the long run.  If nothing else, it would
offer smaller flexibility for those that want to stick with a previous
minor version.

On a somewhat related topic, per our email this morning, I decided to go
ahead and try a build out of RSEL 7 to upgrade the rpi2 kernel, and I
noticed that RSEL 7 doesn't come with any yum repos enabled.  Is there a
yum repo existing for RSEL 7 yet?

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
>



-- 
--Mark
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to