From NWChem
Viewed 943 times, With a total of 5 Posts
|
|
|
Gets Around
Threads 16
Posts 71
|
|
| 2:15:47 PM PST - Sat, Feb 8th 2014 |
|
Hi,
we have discussed this subject already (see http://www.nwchem-sw.org/index.php/Special:AWCforum/st/id329/NWChem_6.1_scalapack_compilat...).
Could you, when making new releases keep the current naming convention:
Nwchem-A.B.revisionC-src.DATE.tar.gz?
The reason for this is that a regex is setup on Fedora packaging page that monitors for new Nwchem releases:
https://fedoraproject.org/wiki/Upstream_release_monitoring#NodeJS_-_O
Monitoring is used to automatically open request for building of new Nwchem RPMS.
Thanks
Marcin
|
|
|
-
Huub Forum:Admin, Forum:Mod, NWChemDeveloper, bureaucrat, sysop
|
|
|
Forum Regular
Threads 1
Posts 185
|
|
| 4:22:18 PM PDT - Tue, Apr 8th 2014 |
|
Hi Marcin,
I have changed the default name that the tarball builder generates. However, I am not sure whether this is exactly the format that you want (I was not part of the previous discussion). So my script now will generate something like:
Nwchem-6.3.revision25464-src.2014-04-08.tar.gz
Is this what you want or do you rather have
Nwchem-6.3.25464-src.2014-04-08.tar.gz
Currently the revision number is simply the subversion revision number of the revision I am tarring up. That is a number I can extract automatically. The usual major.minor.bugfix number is something that needs to be generated by hand which is tedious to do. Please see the build_nwchem_src_distro for what I do. If you want me to do something else, please let me know.
Huub
|
|
|
|
|
|
Gets Around
Threads 16
Posts 71
|
|
| 9:13:39 AM PDT - Tue, May 6th 2014 |
|
Hi,
i was was asking for keeping the naming convention.
The latest naming change resulted in a false positive here:
https://bugzilla.redhat.com/show_bug.cgi?id=1094703
There must be a way to distinguish between a stable release and a development snapshot,
that can be easily extracted using a regular expression. Please see
https://fedoraproject.org/wiki/Upstream_release_monitoring#NodeJS_-_O
Marcin
|
|
|
-
Huub Forum:Admin, Forum:Mod, NWChemDeveloper, bureaucrat, sysop
|
|
|
Forum Regular
Threads 1
Posts 185
|
|
| 10:32:23 AM PDT - Tue, May 6th 2014 |
|
Hi Marcin,
Ok, I see your point. So if I upload new release revisions as
Nwchem-6.3.revision25464-src.2014-04-08.tar.gz
but development snapshots as
Nwchem-dev.revision25464-src.2014-04-06.tar.gz
then the development snapshot is not picked up by your regex but a release revision is.
Shall we do it that then?
Best wishes, Huub
|
|
Edited On 10:33:18 AM PDT - Tue, May 6th 2014 by Huub
|
|
|
|
|
|
Gets Around
Threads 16
Posts 71
|
|
| 4:35:36 AM PDT - Wed, May 7th 2014 |
|
| Yes, let's keep the naming convention you suggest.
|
|
|
-
Huub Forum:Admin, Forum:Mod, NWChemDeveloper, bureaucrat, sysop
|
|
|
Forum Regular
Threads 1
Posts 185
|
|
| 9:52:06 PM PDT - Wed, May 7th 2014 |
|
Hi Marcin,
Just in case anyone is interested: I have updated the script nwchem/contrib/distro-tools/build_nwchem_src_distro such that it will look in the <working directory>/src/config/makefile.h for the setting of RELEASE (only 1 uncommented setting is allowed). If the variable is set to a release number the script will assume that it is generating a release tar-ball and otherwise that it is generating a development snapshot. Based on that and the naming convention described above the script will create a directory and associated tar-ball name. This way all tar-balls should have "standard" names from now on.
Best wishes, Huub
|
|
|
AWC's:
2.5.10 MediaWiki - Stand Alone Forum Extension
Forum theme style by: AWC
