#include <hallo.h> * Eddy Petrişor [Thu, Jun 15 2006, 02:34:07PM]: > On 6/15/06, Eduard Bloch <[EMAIL PROTECTED]> wrote: > >#include <hallo.h> > >* Eddy Petrişor [Wed, Jun 14 2006, 11:00:02PM]: > > > >> Relative paths should be better and not client specific. > >> If one has .svn/deb-layout or some (~/.|/etc/)svn-buildpackage.conf > >> and there are also svn properties, local settings should be > >> prioritary. > >> > >> Ok, the main problem I would like to solve is to have a way to run > >> svn-buildpackage after a fresh checkout of a "package" that has only > >> debian information in SVN. > >> Combining pre-build-action (where a smart sript that fetches the orig > >> tarball if is not present, with origDir pointing to the place of > >> download, the whole preparation could be done automatically (with > >> relative paths). > > > >My feeling says that you forgot to RTFM, the part about the > >debian/svn-deblayout with default settings. Am I right? > > My feeling is that you rushing a litle bit. > BTW, the manual is quite thin on explanations related to fields in the > .svn/deb-layout and actions. Is it possible to have a
Because it is a template for .svn/deb-layout and nothing more. > debian/svn-buildpackage.actions.config ? Possible, yes. Would I add that feature? No. Why? I dislike the idea of adding to many invasive features into the official packages, eg. hidden scripting. That just asks for beeing misused. > Back to the issue at hand, the main desire is to be able to do something > like: > > svn co <some package URI, be it trunk or an old/new tagged release> pack > cd pack > svn-buildpackage > > That happening on a fresh machine while in SVN there is only the > debian/ directory and the orig tarballs are _NOT_ in SVN. You can do that using the hooked actions, as described in the manpage. I am not willing to add such scripting to the official packages. For you special needs, you can simply put a script into debian/ that DWYW and call it instead of pure svn-buildpackage. But that is your personal customisation option. > If that is possible, maybe a couple of examples in the HOWTO would be > good to have, it is not obvious. Manpage describes which instruments svn-buildpackage gives you. Even with multiple examples of how tarball fetching can be implemented. > Note: I consider a debian/svn-deblayout a file in the class of SCM > debris, debris which should not be present in the source package, as > the policy states. That's why I think this info should be present in > svn properties. After the file release nobody will need that file if > the package is apt-get sourced. That's a good point. I will consider making it skip the junk while preparing the build environment. Eduard.
