On 6/24/06, Tim Dijkstra (tdykstra) <[EMAIL PROTECTED]> wrote:
The upstream author
also only provides infrastructure for static linking.
iirc there are ways to make a dynamic library even if upstream only
provides a static one. I think I once saw this method employed for
another debian packag
On Sat, 24 Jun 2006 23:17:08 +0200
Florian Weimer <[EMAIL PROTECTED]> wrote:
> * Tim Dijkstra:
>
> > I need this for static linking in the muswsusp binaries resume and
> > suspend. That's why I only intend to provide the a liblzf-dev. The
> > upstream author also only provides infrastructure for
* Tim Dijkstra:
> I need this for static linking in the muswsusp binaries resume and suspend.
> That's why I only intend to provide the a liblzf-dev. The upstream author
> also only provides infrastructure for static linking.
How is this superior to LZO? Is it just the licensing?
--
To UNSUB
Package: wnpp
Severity: wishlist
Owner: "Tim Dijkstra (tdykstra)" <[EMAIL PROTECTED]>
* Package name: liblzf-dev
Version : 1.51
Upstream Author : Marc Alexander Lehmann <[EMAIL PROTECTED]>
* URL : http://www.goof.com/pcg/marc/liblzf.html
* License : BSD/GPL
P
4 matches
Mail list logo
