On 6/14/06, Eduard Bloch <[EMAIL PROTECTED]> wrote:
#include <hallo.h>
* Eddy Petrişor [Wed, Jun 14 2006, 11:27:24AM]:
> Package: svn-buildpackage
> Severity: wishlist
>
> Hello,
>
> The usage of .svn/deb-layout seems a little bit not-so-comfortable.
Because?
Because is some information which should be related to the package and
version not to one client.
> Probably it would be a good idea to have all the properties in the
Probably? What does that mean? To you wish to have it that way or not?
And if yes, then why exactly?
Yes, for easier group maintainership.
> .svn/deb-layout stored as svn properties. This way an fresh checkout
> could be built imediately and deb-layout information could be
> preserved.
Why? Most of the settings therein are client-specific. Why would you
want to export things like account data and absolut local paths to the
public?
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).
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
