On 06/07/2010 06:34 PM, Yaroslav Halchenko wrote:
> On Mon, 07 Jun 2010, Christian Kastner wrote:
>>>   I doubt there would be ever two versions of libfann*-dev available, and
>>>   it isn't a project with fast changing API ;)
>> Upstream Makefile.{am,in} contain references to the libfann2-dev
>> package. They don't affect our build process in any way, so they could
>> be safely changed.
> yeah -- those seems to be only for composing source distributions by
> upstream
> 
>> I'd prefer libfann-dev too, but didn't want to deviate from upstream too
>> much. If you think it's safe to change, I'll do it.
> should be safe, but ideally I would have made a tiny patch on top of
> Makefile.*, include it in debian/patches, ship it upstream and check
> what he would think about it -- may be he had some higher visions?  but
> that might take awhile to get a reply, so to expedite I don't mind
> leaving it as is... and thus up to your decision.

I noticed that I had to patch Makefile.am anyway, to reflect other
changes (eg libfann-py rename). I added a patch 0003 implementing this.

Since that left nothing in the way of renaming to libfann-dev, I just
did that, and applied the necessary changes to debian/*.

>> The changes were applied to git, I'll wait with rebuilding/uploading
>> the source package for your opinion on libfann?-dev.
> make your own decision, and gimme url to .dsc -- I think we could
> try getting through NEW (since there was libfann1-dev, I guess
> ftpmasters shouldn't complaint much about libsvm2-dev).

I just built and tested the packages. The source package has been
uploaded to m.d.n:

http://mentors.debian.net/debian/pool/main/l/libfann/libfann_2.1.0~beta~dfsg-1.dsc


Regards,
Christian



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to