🚀 go-pugleaf

philh@vision25.demon.co.uk (phil hunt) writes:

> Yes, I know. And when parrot-0.2.5.tgz is untarred, it'll create a directory
> parrot-0.2.5/ under the cwd to put the contents in.

Goodie. Sounds like the right way to do things.

> >the alternatives are either full directory paths (EVIL! [1]) or no
> >directories at all ( cd blah-0.2 ; tar cvzf ../blah-0.2.tar.gz * )
> >according to taste.
> 
> Isn't writing tar files so they untar into the current directory considered
> a no-no?

Probably. It's something that I've almost got into the swing of with decent
open-source auto{make,conf}-produced Stuff, that it will create its own
package-version/ directory, although I'm not aware of any unifying
directive. (And there's a fair bit of stuff that *isn't* that polite, too,
which means a   tar tvzf thingy.tgz | head   never goes amiss... grr)

> >> Is there an easier way?
> >
> >   -1) that IS easy!  ;8^]
> >    0) not really unless you do something graphically eg with kfm / whatever
> >    1) you are using tab-completion, aren't you?
> >    2) are you only copying certain files across from parrot/ each time? if
> >       so, why not live under parrot-0.2.5/ in the first place?
> 
> Because parrot/ contains my working version of the Parrot program. If the
> last release was 0.2.5, and i make changes, the current version isn't
> 0.2.5 any more (I use the notation "0.2.5+"). So I'd have to continually
> keep mv'ing my directory names. I suppose i could, but I don't really
> want to.

ln -s  ? ;)

> In any case, having separate directory structure for each release as they
> are made works as a primitive form of version control (CVS is a bit over
> the top for a one-programmer project IMO).

Fair does (now I understand where you're approaching this from! :) 
I've not worked with CVS over much, so can't comment on the suitability for
a 1-person setup. Depends on size of project as well, I guess.

> >    3) can you automate the list of files you move across? If so, stick
> >       it in a shell script
> 
> This is sensible.
> 
> >    4) can you generate a list of files by a set of rules, eg "isn't a
> >       .o file and was modified in the last 4 days"? If so, use find
> >       like this:
> >	find parrot/ -mtime -4 ! -name \*.o -exec cp {} parrot-0.2.5/ \;
> 
> Sort of. For example, for parrot I want to copy all *.py files but no
> *.pyc ones.

Rightyho. Some little shell-script that takes a few args / default values /
environment variables and copies the directory to one suited to packaging
and then does a 'make clean' in it and/or strips out any unwanted files,
etc? Or the build-it-up-as-required approach, whichever involves less
thinking :)

~Tim
-- 
| Geek Code: GCS dpu s-:+ a-- C++++ UBLUAVHSC++++ P+++ L++ E--- W+++(--) N++ 
| w--- O- M-- V-- PS PGP++ t--- X+(-) b D+ G e++(*) h++(*) r--- y-	     
| The sun is melting over the hills,         | http://piglet.is.dreaming.org/
| All our roads are waiting / To be revealed | piglet@glutinous.custard.org