On Wed, Apr 09, 2008 at 12:28:32PM -0500, inode0 wrote:
> Recent (at least recently noticed by me) changes in the way Red Hat is
> versioning rpms had an unexpected negative impact on some of our
> custom packages that replace RHEL base channel packages. What we do is
> a rather long story and not very relevant to my question which is more
> about consistency and understanding what Red Hat is doing when they
> version and re-version rpms they provide.
>
> $ rpm -q --qf "%{RELEASE}\n" gnome-screensaver
> 6.el5
>
> That is typical of how things have been and minor updates bumped
> something before the .el5 bit.
>
> $ rpm -q --qf "%{RELEASE}\n" cups
> 11.14.el5_1.6
>
> This is showing up more and more and minor bumps are occurring after
> the .el5 bit.
>
> Rather than explaining how this affects the way I version packages
> locally could someone just explain the actual way Red Hat is now doing
> package versioning so I can adjust?
>
> Thanks,
> John
>
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
I have to second this. I've been bitten minorly by some similar changes
in the release field.
I've made it a practice and even automated building packages with the
dist tag and I too am confused about why there are multiple release tags
in RHEL5. Should I expect (code for) 'el5' or 'el5' and all the 'el5_X'
for each point release?
Also, the adding extra release increments after the release tag. Can
that be cleaned up?
Jack
--
Jack Neely <[EMAIL PROTECTED]>
Linux Czar, OIT Campus Linux Services
Office of Information Technology, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
