Ryan Niebur dijo [Sun, Aug 02, 2009 at 03:10:32PM -0700]:
> of course. :)
> 
> so our (the perl group) layout is like this:
> tags of uploads: 
> svn+ssh://svn.debian.org/svn/pkg-perl/tags/libany-moose-perl/0.07-1/
> trunk: svn+ssh://svn.debian.org/svn/pkg-perl/trunk/libany-moose-perl
> 
> this is my first proposed change. we would probably also switch from
> packages-wip to just a single trunk with this change. what's the
> benefit of packages-wip anyway? It seems to just create more work
> because you can't check that your Vcs-* fields are correct on the
> first upload, and you have to do the extra "svn mv" and "svn switch".
> 
> we (the perl group) also keep upstream source in svn, which is a lot
> more convenient because you don't need to extract the source manually
> to add a quilt patch, for example. it doesn't add much size, and we
> have a lot more packages than DRE. I'd like to propose we do this as
> well, tho this is unrelated to my first proposed change.
> 
> I'd be willing to do the switchover, update the documentation, and
> send an email explaining what people will need to change in their
> current workflows for either of these changes.
> 
> So what do people think? please tell me which of the 3 changes you
> think should happen (toplevel trunk/tags, single trunk instead of
> packages-{,wip}, upstream source in svn). the first one would solve
> the original reason for this thread, the other two would just make
> things simpler on us (afaict).

Full (and expected, and late) "ME TOO" to Ryan. I also prefer having
the full packages available to work in the tree, even though it bloats
it a bit. 

About -wip: Agree, with PET, PET takes care of drawing attention to
where it is needed, showing which packages have never yet been
uploaded. 

I'm late, so I must leave _now_.

-- 
Gunnar Wolf • [email protected] • (+52-55)5623-0154 / 1451-2244

_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers

Reply via email to