Hi,
On Thu, Apr 2, 2009 at 4:25 PM, Ron Pinkas <[email protected]> wrote:
> I don't understand, what problem do we have with cmd.exe?
>
> Don't we just need to add few more calls to zip command for the missing
> files?
If we go this way we will need to add few more calls whenever a new
directory or files with unsupported extensions are added to the
repository, and remove some calls whenever we remove a directory. What
my script does is:
0. checkout a clean CVS tree with given tag.
1. determine 'binary' files using */CVS/Entries. These files should be
added as binary to zip archive, the rest - as text, so that EOL format
difference on DOS and UNIX is respected. Probably you don't have to do
it to make Windows sources under Windows, but have to do it to make
Unix sources undet Windows or Windows sources under Unix.
2. remove all directories named CVS.
3. move contrib and tests subdirs out of the main tree. This is
because of our tradition to provide separate archives for them.
4. rename main directory to xharbour-${VERSION} where ${VERSION} is 1.2.1 now.
5. make .tar.gz archive of xharbour-${VERSION} dir.
6. make zip archive with binary files from xharbour-${VERSION} dir.
7. add text files to the zip archive with -l zip option which changes
EOLs to DOS style (remember, I'm doing it under Unix where CVS checks
out text files with Unix EOLs)
8. rename xharbour-${VERSION} to xharbour-core-${VERSION}.
9. create a fresh xharbour-${VERSION} and move contrib there, so that
we have xharbour-${VERSION}/contrib
10. repeat steps 5,6,7 creating xharbour-${VERSION}.src.contrib.(tar.gz|zip)
11. rename xharbour-${VERSION} to xharbour-contrib-${VERSION}.
12. create a fresh xharbour-${VERSION} and move tests there, so that
we have xharbour-${VERSION}/tests
13. repeat steps 5,6,7 creating xharbour-${VERSION}.src.tests.(tar.gz|zip)
I make xharbour source packages using this script since
xharbour-0.99.60, and all I had to change is version name and CVS tag
name.
Probably someone who speaks cmd.exe language well could implement it
as a Windows batch file. My .bat experience is still on the
command.com or 4DOS level, and I don't know how that EOL trick can be
done under Windows.
-- Ph.
------------------------------------------------------------------------------
_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
