[opensuse-packaging] condition test for a local build?
All, I need to have a pre-compile test that only runs if it is a local build. How do I do that? == details I maintain one package (python-plaso) that comes with a optional pre-compile test module to verify that for 6 specific libraries the latest available libraries are installed prior to building. It's a python script that looks on the Internet for the latest available tarballs for the 6 libraries. LIBYAL_URLS = { 'libevt': 'https://googledrive.com/host/0B3fBvzttpiiSYm01VnUtLXNUZ2M/', 'libevtx': 'https://googledrive.com/host/0B3fBvzttpiiSRnQ0SExzX3JjdFE/', 'liblnk': 'https://googledrive.com/host/0B3fBvzttpiiSQmluVC1YeDVvZWM/', 'libmsiecf': 'https://googledrive.com/host/0B3fBvzttpiiSVm1MNkw5cU1mUG8/', 'libregf': 'https://googledrive.com/host/0B3fBvzttpiiSSC1yUDZpb3l0UHM/', 'libvshadow': 'https://googledrive.com/host/0B3fBvzttpiiSZDZXRFVMdnZCeHc/', } I maintain all 6 of those too, so when I build python-plaso locally, I'd like it to bark if those are out of date. Alternatively, there are about 25 similarly structured libraries (libyal - yet another library). What would need to be done for the auto-version checker for factory to notice there is a new tarball and put in my routine factory status email? (That may already work, the download tarballs being hosted on a googledrive is something that just started a few months ago and I am just now updating the DL_URL fields in my spec files. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 2013-07-30 00:29, Greg Freemyer wrote:
What would need to be done for the auto-version checker for factory to notice there is a new tarball and put in my routine factory status email?
Somewhere, somewhere is a list that contains package <-> watchurl associations. Of course it would be much better if the watchurls would rather be directly drawn from specfiles. #Freecode-URL: http://freecode.com/projects/12345678 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, Aug 1, 2013 at 10:12 AM, Jan Engelhardt <jengelh@inai.de> wrote:
On Tuesday 2013-07-30 00:29, Greg Freemyer wrote:
What would need to be done for the auto-version checker for factory to notice there is a new tarball and put in my routine factory status email?
Somewhere, somewhere is a list that contains package <-> watchurl associations. Of course it would be much better if the watchurls would rather be directly drawn from specfiles.
#Freecode-URL: http://freecode.com/projects/12345678
So the various specfile conventions like #DL-URL are for human use only? Is making it so that they are used a big enough challenge to qualify as a Google Summer of Code project for 2014? It just seems like something that not only could be done, but should be done. Is there an existing fate entry? Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thursday 2013-08-01 16:36, Greg Freemyer wrote:
Somewhere, somewhere is a list that contains package <-> watchurl associations. Of course it would be much better if the watchurls would rather be directly drawn from specfiles.
#Freecode-URL: http://freecode.com/projects/12345678
So the various specfile conventions like #DL-URL are for human use only?
Well, # are comments in specfiles and ignored by rpm itself, but could be parsed by external tools (like #!BuildIgnore) or just be used by humans. For example, I add a #Git-Clone: at times, so that I do not have to go searching for the link on homepages all the time - because some projects have it under "Development" - and others bury it in the depths of their wiki like https://fedorahosted.org/sssd/wiki/DevelTutorials . DL-URL however is used for two purposes currently (download directory view aka "Index of", and actual original file).
Is making it so that they are used a big enough challenge to qualify as a Google Summer of Code project for 2014? It just seems like something that not only could be done, but should be done.
Yes, and shasum for verification should also be placed into the spec file, ideally right next to the Source: lines (in something like "#Source2(sha512): abcd...") rather than in a separate file to reduce duplication anomalies.
Is there an existing fate entry?
No. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Jan Engelhardt <jengelh@inai.de> [2013-08-01 16:12]:
On Tuesday 2013-07-30 00:29, Greg Freemyer wrote:
What would need to be done for the auto-version checker for factory to notice there is a new tarball and put in my routine factory status email?
Somewhere, somewhere is a list that contains package <-> watchurl associations. Of course it would be much better if the watchurls would rather be directly drawn from specfiles.
See the three upstream-*.txt files at https://gitorious.org/opensuse/osc-plugin-collab/trees/master/server/upstrea... In addition there is packagehunter http://gitorious.org/opensuse/packagehunter/trees/master which directly sends mails to package maintainers. If you want to run your own, I also have an easy-to-use crawler which can spit out JSON, HTML+RSS Feeds or TSV tables. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Greg Freemyer -
Guido Berhoerster -
Jan Engelhardt