Malte Forkel wrote:
> Sandro Tosi schrieb:
>> A general rule may be: patch upstream source code, not debian packaging file.
>>
>> Regards,
>
> Well, my patch is active if its in 00list :-)
>
> But you're right, adding the dependency to debian/control is safe and
> easy. It just "doesn't feel rig
On Wed, May 20, 2009 at 02:28:52PM +0200, Malte Forkel wrote:
> an optional patch that I'd like to add to a package requires an
> additional build dependency. If I append that dependency to
> Build-Depends in debian/control as part of my patch, it is not checked
> in time. It seems, the build depe
Sandro Tosi schrieb:
> On Wed, May 20, 2009 at 14:28, Malte Forkel wrote:
>> Hi,
>>
>> an optional patch that I'd like to add to a package requires an
>> additional build dependency. If I append that dependency to
>> Build-Depends in debian/control as part of my patch, it is not checked
>> in time
On Wed, May 20, 2009 at 14:28, Malte Forkel wrote:
> Hi,
>
> an optional patch that I'd like to add to a package requires an
> additional build dependency. If I append that dependency to
> Build-Depends in debian/control as part of my patch, it is not checked
> in time. It seems, the build depende
Hi,
an optional patch that I'd like to add to a package requires an
additional build dependency. If I append that dependency to
Build-Depends in debian/control as part of my patch, it is not checked
in time. It seems, the build dependencies are checked (by debuild) or
checked and satisfied (by pde
5 matches
Mail list logo