Re: MergeOnUpstream and team policy
On 18/07/07, Miriam Ruiz <little.miry@gmail.com> wrote:
>
> 2007/7/18, Eddy Petrișor <eddy.petrisor@gmail.com>:
> > I would like to take on Joey's proposal with some restrictions:
> > - not all packages, I am sure that games like wormux will be huge
> > - I want to see this first in a branch; joeyh, feel free to make a
> people/joeyh branch and work in there
> >
> > The main reason for this decision was space taken by the repo. This is
> still a big concern for me and I am sure for
> > others too.
> >
>
> What are the implications of accepting his proposal, and in which way must
> we redefine the way we're doing things right now? I think it should be
I thought it was clear that I wouldn't mind an experiment in a branch
to see the size difference. I constantly keep a full trunk checkout in
my ~/usr/src/games/trunk directory and I am struggling with size
issues on a montly basis. A trunk size increase would certainly make
my life harder and probably others', too.
I think that keeping the patching system has a clear benefit which is
understanding clarly without any svn server access what debian
specific changes were done and why. Dropping quilt/dpatch would be a
mistake imho.
> clear for everyone where this will lead us to before doing it. Does it mean
> we won't have to restrict our changes to debian/, quilt (or, exceptionally
> dpatch) is not mandatory anymore and we can switch back to old .diff.gz
> files and so on, or that we'll keep having all the stuff in debian/ as we do
> now, and the rest of files outside that directory would be unmodified from
> upstream?
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
Reply to: