[Pkg-amule-devel] Task list for November

[Adrián Yanes]

Sandro I know that the common packages are a strong dependency.

But I only worked with packages that didn´t need a extra package for
common files.  I was checking the debian/rules and now I understand
your point.

Please consider that aMule it´s my first "big" package and some rules
are new for me.

Thanks for your supervision, is too helpful.

Regards.



2009/11/1 Sandro Tosi <morph at debian.org>:
> On Sun, Nov 1, 2009 at 17:05, Adrián Yanes <devel at ayanes.com> wrote:
>> HI Sandro. thanks for your fast response.
>>
>> Thanks for the explanation of the branchs.
>
> you're welcome :)
>
>> The phrase of new features was speaking about the aMule program not
>> package.  The correct expression it´s to update the version of package
>> ( 2.2.5-1.1 ==> next upstream).
>>
>> I going to start with the new upstream (2.2.6).
>>
>> And we should consider  to update also amule-common no ?
>
> 'amule' is the source package, the one you're going to update to the
> new upstream release; 'amule-common' is a binary package, made from
> 'amule' (the source package, because there is also an 'amule' binary
> package), that will be installed on the users systems, and it will be
> updated the moment you update 'amule' src.
>
> If it's not clear (as it seems from your question) you'd better study
> a bit how debian packages work.
>
> Regards,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>