I had hoped to save some data transfer by using buildrelease to rebuild the 2.0.0pre5 tarball from local cvs, but it seems to think we are on 1.9.3 still. Does anyone have an easy way to make it build the released 2.0.0pre5? -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
MJ Ray wrote:
I had hoped to save some data transfer by using buildrelease to rebuild the 2.0.0pre5 tarball from local cvs, but it seems to think we are on 1.9.3 still. Does anyone have an easy way to make it build the released 2.0.0pre5?
It's just version guessing that is wrong (i don't know why : it worked. I'm not a shell-script/cvs specialist, so I don't understand how it works. However, when buildrelease tries to find the release number, just enter <ok>, then 2.0.0pre5, and it works fine, creating a release from local CVS. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-11-03 15:50:32 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
However, when buildrelease tries to find the release number, just enter <ok>, then 2.0.0pre5, and it works fine, creating a release from local CVS.
This seems to build a version labelled "2.0.0pre5" that is really CVS HEAD. I am not sure what the non-trivial parts of buildrelease do or what they should be doing. Are all files in CVS used for the tarball?
MJ Ray wrote:
On 2003-11-03 15:50:32 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
However, when buildrelease tries to find the release number, just enter <ok>, then 2.0.0pre5, and it works fine, creating a release from local CVS.
This seems to build a version labelled "2.0.0pre5" that is really CVS HEAD. I am not sure what the non-trivial parts of buildrelease do or what they should be doing. Are all files in CVS used for the tarball?
afaik, the buildrelease : * updates the local copy of CVS. * IF ASKED, tags the files in CVS with the release number. * creates a tar.gz from the local copy. So, even if there are local files that are NOT in cvs server, they are in the release. Same thing if there are local files that have not been commited to server (they are tagged in a version different than the real released file). I try to avoid this by looking carefully at the initial cvs update HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (2)
-
MJ Ray -
paul POULAIN