Hi,
> Well, is just another layout style I've seen in some repositories for
> collaborative maintainance of packages (e.g. the svn repository of ocaml
> maintainers).
>
> > (dpkg-buildpackage will need ../upstream there, right?)
>
> No, you can use {cvs,svn}-buildpackage in merge mode which creates
> debianized source trees just before invoking dpkg-buildpackage.
Isn't that the place to add hooks to copy orig.tar.gz and source
tree to the appropriate places?
> > I don't think dpatch is the correct place to support having
> > ../upstream.
>
> I agree it might open the road to everyone asking why not look for
> .orig.tar.gz also here and there ...
>
> What about adding a configuration option (e.g. "origtargz_path") which
> could be put in .dpatch.conf whose semantics is to list all directories
> where dpatch-get-origtargz should look for .orig.tar.gz before falling
> back to apt-get source?
>
> It would be a flexible sollution which wont pollute dpatch's code.
Flexible, but
1. it only copies a file to another place, which I doubt is any
good for the maintenance
2. I doubt that it's a good idea to increase options on dpatch side just
to make that happen.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
