Re: your mail
Hi Yaroslav,
After learning some Makefile.am-fu, aghermann-0.4.3.2 is now
lintian-clean: the single remaining .so file is stowed into
/usr/lib/aghermann. Please have a look at sf.net/projects/aghermann
or review it online at gihub.com/hmmr/aghermann (there is an
-amd64.deb, too).
What do I do next? Whatever I do, I understand the powers that be
would first approve my project at alioth, right? I am patiently
waiting for this to happen, sigh..
Cheers,
Andrei
On 11 December 2011 17:31, Yaroslav Halchenko <debian@onerussian.com> wrote:
> Hi Andrei,
>
> Great -- thanks.
>
> Since the library is "internal" ideal resolution imho would be to hide
> it away under usr/lib/aghermann/ and link all binaries against it
> (rpath). that should take care about lintian issues ;)
>
> On Sun, 11 Dec 2011, andrei zavada wrote:
>
>> Hi Yaroslav,
>
>> I have fixed all lintian issues with Aghermann except this one:
>
>> W: aghermann: package-name-doesnt-match-sonames libsigfile0
>> W: aghermann: non-dev-pkg-with-shlib-symlink usr/lib/libsigfile.so.0.0.0 usr/lib/libsigfile.so
>
>> This libsigfile is an internal library which is used by the main
>> executable (aghermann) and by two accessory programs contained in the
>> same package. I tend to think splitting the whole project in three
>> (aghermann, libsigfile and aghermann-tools) would be a little overkill,
>> and that simply overriding this warning might be sufficient, for now.
>> What do you think?
>
>> Other than that, as of the latest version (0.4.3.1) Aghermann is ready
>> for packaging AFAICT. I am still waiting for the admission approval from
>> Alioth admins, though.
>
> --
> =------------------------------------------------------------------=
> Keep in touch www.onerussian.com
> Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
Reply to: