On Thu, 2010-12-30 at 00:53 +0100, Jonas Smedegaard wrote:
> On Wed, Dec 29, 2010 at 08:14:57PM -0300, Felipe Sateler wrote:
> >You edited debian/control, but Jonas added debian/control.in for 
> >build-dependencies autogeneration. If you disagree about the use of 
> >debian/control.in, we should disable it. If not, we should use it. But 
> >having it and not using it does not seem a sane option.
> I suggest we only drop the control.in if noone use the .in file or it 
> annoys someone.
> I see no big problem in some of us editing the control file directly - 
> the nuissence of sync'ing changes there to the .in file is shadowed by 
> the benefit of dependency semi-autoresolving IMO.
> (please do edit the .in file rather than the control file if you want to 
> help minimize work for everyone, though)

Ok, I hope its alright with everyone, I removed the control.in.  I can
see using automatic build-depends generation on a package with complex
Build-Depends, but this one is really simple, and I think the
Build-Depends will rarely change, if ever.

>From my experience, build products should not be in git (i.e. the
'control' file generated using 'control.in').  Since that doesn't seem
possible for 'control', I think we'll be better off by simplifying to a
static 'control'.


pkg-multimedia-maintainers mailing list

Reply via email to