Re: Standard build process
On 24/09/06, Miriam Ruiz <email@example.com> wrote:
--- Eddy PetriÅŸor <firstname.lastname@example.org> escribió:
> I have written a small document about standardised build process for
> our packages and sumarised benefits and problems that need to be
> solved before we can implement this properly.
> Please read, comment and correct the document:
It's a great idea. It would be nice to comment some things a bit more in
detail though, as I've never used svn-buildpackage too much (and, if possible,
(feel free to add any part of this info to the wiki page)
it would be nice to support it but not to make it strictly neccesary), I get a
bit confused with all those origURL tags, svn-bp properties and so. Where are
they supposed to be or how can we add them? Or is it the client who must add
origUrl = the field that should specify where the orig tarball is
available; is a http or ftp URL; the filename MUST be in debianized
form (e.g.: the origUrl of foo 1.02-4 can be
origUrl support is currently NOT implemented in svn-buildpackage
origUrl-s are specified currently for a few packages which are in our
repo as the value of the svn-bp:origUrl property.
Adding, reading and modifiyng them is explained in the subversion
manual at the dedicated chapter.
Subversion has reserved the following property names: svn:executable,
svn:mime-type, svn:ignore, svn:keywords, svn:eol-style, svn:externals,
svn:special, svn:needs-lock. Every peroperty name starting with "svn:'
is also reserved to Subversion.
 it is customary to prefix the properties' names with something,
here "svn-bp", to avoid name colisions and implement some kind of
namespaces; Subversion itself uses "svn" as a prefix; I proposed
"svn-bp" in order to suggest "svn-buildpackage" namespace.
 In order to see which properties a file or directory has (e.g.
foo), one should type "svn pl foo" ; to see the value of the property
called "has-muscles" of "foo" one has to type "svn pg has-muscles"
"Imagination is more important than knowledge" A.Einstein