You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
David, you were half way through moving from individual deb/rpm scripts. the script package-lib needs work, in particular -
It does not correctly make the rpm package because the final part of version number is not being inserted into the spc file, we end up with a spec file containing "INSERT_EXTRAVER" and "INSERT_FULL_VER".
The rpm-package script, on the other hand, does not make a correct devel rpm file, it leaves the dev symlink with a stupid long path prepended to the target file name. package-lib does this properly !
This sure is a "can do better" !
David
The text was updated successfully, but these errors were encountered:
Yes, using the individual script, rpm_package, the devel.rpm contains a symlink that is plainly wrong. Fixed and used to make 1.2.14 in release but I have not committed the fixed script yet. Need to workout whats going on with package-lib first. The package-lib script is, ultimately, the one to use and might have other content not present in the two individual ones. Further work needed....
OK, package-lib now seems to work as expected. Further, it now accepts a whatsnew file to populate the changelog (much like I do in tomboy-ng).
I'll wait until I have done some tests before closing this issue.
David, you were half way through moving from individual deb/rpm scripts. the script package-lib needs work, in particular -
It does not correctly make the rpm package because the final part of version number is not being inserted into the spc file, we end up with a spec file containing "INSERT_EXTRAVER" and "INSERT_FULL_VER".
The rpm-package script, on the other hand, does not make a correct devel rpm file, it leaves the dev symlink with a stupid long path prepended to the target file name. package-lib does this properly !
This sure is a "can do better" !
David
The text was updated successfully, but these errors were encountered: