[Bug 1039] New: LSB packaging doesn't handle LSBVERSION right

[email protected]
Newsgroups gmane.linux.lsb.test-suite
Message-ID <[email protected]>
OtherBugsDependingO 613
             nThis:


In the packaging directory, the handling of LSBVERSION is messed up.  LSBVERSION
needs to be passed down into all the checker builds unchanged, so that it can be
reported correctly by the checkers.  Instead, we're two steps removed from that:
Makefile.common stuffs more than the base version in when it's constructing the
.spec from the .spec.sed:

sed -e "s#@LSBVERSION@#`echo $(LSBVERSION)$(SUB_VERSION)$(VERSION_SUFFIX)`#" -e
"s#@PACKAGE_RELEASE@#`echo $(RPM_PACKAGE_RELEASE)`#" < $< > $@

And then the individual .spec files don't even use it:

CC=/opt/lsb/bin/lsbcc make LSBVERSION=${RPM_PACKAGE_VERSION}
LSBCMDCHK_VERSION=${RPM_PACKAGE_VERSION}-${RPM_PACKAGE_RELEASE}

Instead, the main decision made in the .spec.sed (and thus .spec) based on the
edited in LSBVERSION is the name of the tarball.

Each checker has a {CHECKER}_VERSION in addition to LSBVERSION internally. When
printing both of these out from a snapshot build, we get:
lsbcmdchk 3.0.3.20050702-1 for LSB Specification 3.0.3.20050702
and we can see the problem. In fact, the LSBCMDCHK_VERSION in this case isn't
right either, as it's a snapshot it should in some way indiciate unofficial
beyond just having a date suffix.   
 
--    
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email   
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.