search

supersdar / collide

Automatically exported from code.google.com/p/collide
Apache License 2.0
0 stars 0 forks source link

Need top level ant target to produce a binary (was: Release tarball does not have containing directory) #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. cd ~/src
2. tar -xvf ~/Downloads/collide-dist-2012-07-07.tar.bz2
3. mutter, then clean up all the trash that's been littered in my src directory.

What is the expected output? What do you see instead?
100s of lines like:
./collide-dist-2012-07-07/bootstrap.js

instead I see 100s of lines like: 
./bootstrap.js

What version of the product are you using? On what operating system?
2012-07-07, linux.

Please provide any additional information below.
Always include the containing directory in tarballs.

Original issue reported on code.google.com by step...@thorne.id.au on 10 Jul 2012 at 8:28

GoogleCodeExporter commented 8 years ago 
Sorry, we actually have no scripts right now (or ant build rules) that produce 
a binary.  I just handrolled them.

Patches welcome.  Ideally, you should be able to type something like:

ant tarball

And get a 'collide-<date>.tar.bz2' that contains everything in bin/deploy but 
root internally at 'collied-<date>/'

Original comment by dragonsinth on 11 Jul 2012 at 4:22