Puppy Linux Discussion Forum

Pizzasgood · Posted: Tue 13 Oct 2009, 13:06 Post subject:

From http://www.murga-linux.com/puppy/viewtopic.php?p=350864#350864:

technosaurus · Joined: 18 May 2008 Posts: 3843

I've been thinking of how to organize this also, not just for source code but also for package maintenance.

---[Extras (pinstall.sh, .desktop, pixmaps, additional scripts.... in a proper tree so it can be directly copied)

---[src (for puppy projects or non compiled programs) Outside projects would have a file with a link to the main project

...Notes_Changelog (best configure options, files to add/modify/delete after compile, other nuances,...)

...config file (contains the compile options used to best compile the program)

...Latest_stable_pet(s)??<-- How fast would we use up 1GB - Google would likely increase the limit but....still maybe just a link

What else is missing? I would like to build a tree with the basic stubs already there.

Pizzasgood · Posted: Tue 13 Oct 2009, 13:50 Post subject:

Something to be wary of: SVN likes to place a hidden .svn/ directory inside of every directory in the repository. So if you set up a tree expecting to literally copy/paste it into a build environment or compress it into a package, you need to either use something like 'svn dump' (I think, haven't looked at it in a while), or else run a script on a copy of the data to remove all .svn/ directories (don't do that to the originals in the SVN working dir or you'll break it).

That's one of the reasons I organized the Edit-SFS project as I did (no directories, and a Makefile to put everything together) even though it doesn't actually have anything to compile. When I want a directory tree I can just run make dir and it appears, nice and clean. I can use make pet to make a .pet. I can use make clean to clear all that out and restore me to a clean SVN checkout.

Also, IIRC SVN doesn't work with device nodes, and probably not with permissions, so if you make a package that contains dev nodes or files that need special permissions, you'll have to have the pinstall.sh script create/set them or something.

technosaurus · Joined: 18 May 2008 Posts: 3843

Good pointer/hack PG. Can't you also use tar to exclude .svn somehow when making a tarball? I don't recall the option. I will definitely have to test the permissions though - That would not be good. (If so, your Makefile option should get around permissions also, assuming appropriate chmod is set up in the Makefile, correct?)

Pizzasgood · Posted: Tue 13 Oct 2009, 15:09 Post subject:

tar --exclude-vcs will do the trick. I didn't know about that. Cool.

You can also use rsync instead of cp when copying things to filter out directories matching a pattern, but you have to be a lot more careful about how you write the target and destination names with rsync (it attaches significance to the presence of a trailing / to determine how you want to copy things (renaming, copy into, copy over, etc.)).

I just did some quick testing, and apparently SVN will track the execute bit when a file is added but not after the file exists. The other bits were all ignored.

Aitch · Joined: 04 Apr 2007 Posts: 6825 Location: Chatham, Kent, UK

here's a link needs some comment, please

mikeb · Joined: 23 Nov 2006 Posts: 4378

Erm no issues on the bugtracker and I had another I had found.....what's happening

mike

technosaurus · Joined: 18 May 2008 Posts: 3843

The direct link still works... The wiki page for "issues" overrides the issue tracker list. This is a good place for a "how to file a good bug report" message. I made a quick temporary edit that points to the actuall issue list

mikeb · Joined: 23 Nov 2006 Posts: 4378