Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Ubuntu 10.04 LTS on IBM Lenovo R61e, RHEL5-6,SLES10-11
Posts: 262
Rep:
version vs release RPM package
Hi
Trying to understand version nr. of RPM package and release nr.
I have the following package e.g. tree-1.5.3-2.el6.x86_64.rpm.
tree ---> package name
1.5.3 ---> version
2 ---> release
e16 ---> operating system major version
x86_64 ---> cpu architecture
What is the difference between version nr vs release nr ?
AFAIK the version number is the released version of upstream application foo and the release number is the built of RPM package foo. Say releasing upstream foo-0.1.4 creates foo-0.1.4-1.rpm. Patching upstream foo-0.1.4 then would be foo-0.1.4-2.rpm.
Distribution: Ubuntu 10.04 LTS on IBM Lenovo R61e, RHEL5-6,SLES10-11
Posts: 262
Original Poster
Rep:
Quote:
AFAIK the version number is the released version of upstream application foo and the release number is the built of RPM package foo. Say releasing upstream foo-0.1.4 creates foo-0.1.4-1.rpm. Patching upstream foo-0.1.4 then would be foo-0.1.4-2.rpm.
I thought that patching upstrem would change version number from e.g. foo-0.1.4 to foo-0.1.5 ?
What means patching upstream in this example ?
The minor/build version is the version RHEL created with patches added by RHEL not in the upstream version (major ver num).
RH usually contributes the patches to the upstream provider, but if they are RHEL specific then they won't be added into the upstream version.
You may find chap 10, 11 useful http://www.linuxtopia.org/online_boo...ion/index.html
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.