On 04/09/2015 12:25 AM, Mark Campbell wrote:
> 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?
>
At the time I made the redsleeve-release rpm I had no clue how and where
the yum repo would be, so there is no yum configuration in there.

That being said, you should be able to create a
/etc/yum-repos.d/RedSleeve.repo with content like:
[Redsleeve_alpha]
name=RSEL7 alpha repo
baseurl=http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/alpha/
enabled=1
gpgcheck=0

[Redsleeve_alpha_updates]
name=RSEL7 alpha updates repo
baseurl=http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/alpha-updates
enabled=1
gpgcheck=0


We have not yet automated the upload process to here, so a little more
up-to-date things (including the 7.1 work-in-progress) can be found here:
ftp://jacco.ligthart.nu/Redsleeve7/

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

Reply via email to