wonder if I can do something about it in Wine. Is
there a way for Wine to declare a conditional dependency, where it
says if you have libnss-mdns, you also need lib32nss-mdns - or in other
words, if you want Wine, you need both installed or both uninstalled.
Something like Depends: lib32nss-mdns
[Stephen Gran]
I really hope that's not true. There are many useful use cases for
static linking when you're building for constrained or otherwise not
quite sane environments that IMHO we should continue to support.
Since in the main it's not that hard to do the right thing, it's
also of
On Mon, Feb 25, 2008, Steve Langasek wrote:
Conventionally, library -dev packages do depend on other -dev packages that
they require for static linking; and certainly, tools like pkg-config and
libtool (and other home-grown foo-config scripts) tend to encourage this
behavior. Nowadays, with a
On Mon, Feb 25, 2008, Nikita V. Youshchenko wrote:
And what if somebody will try to link statically?
Your -config binary should gain a --static flag to distinguish between
the two uses.
--
Loïc Minier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
This one time, at band camp, Petter Reinholdtsen said:
[Stephen Gran]
I really hope that's not true. There are many useful use cases for
static linking when you're building for constrained or otherwise not
quite sane environments that IMHO we should continue to support.
Since in the main
On Tue, Feb 26, 2008 at 12:03:06PM +, Stephen Gran wrote:
This one time, at band camp, Petter Reinholdtsen said:
[Stephen Gran]
I really hope that's not true. There are many useful use cases for
static linking when you're building for constrained or otherwise not
quite sane
On Tue, Feb 26, 2008 at 11:26:30PM +1100, Hamish Moffatt wrote:
What are the constrained environments where you think static linking
would be useful? I'm developing embedded systems and I prefer shared
libraries - unless you have only one application using a particular
library then you will
On Mon, Feb 25, 2008 at 11:07:10PM +, Roger Leigh wrote:
I stopped providing static libraries in all my library packages quite a
while back. No one used them, and they were just needless bloat. I
can't say I would be upset if we dropped all the static libraries from
the entire
Hi
I maintain libetpan package, which build-depends on libcurl4-gnutls-dev.
Resulting library package dependency is calculated using ${shlib:Depends},
however libdev package dependency on libcurl4-gnutls-dev is manually
written in debian/control file. The build package dependency is valuable
On Mon, Feb 25, 2008 at 10:56:09PM +0300, Nikita V. Youshchenko wrote:
Hi
I maintain libetpan package, which build-depends on libcurl4-gnutls-dev.
Resulting library package dependency is calculated using ${shlib:Depends},
however libdev package dependency on libcurl4-gnutls-dev is manually
On Mon, Feb 25, 2008 at 10:56:09PM +0300, Nikita V. Youshchenko wrote:
I maintain libetpan package, which build-depends on libcurl4-gnutls-dev.
Resulting library package dependency is calculated using ${shlib:Depends},
however libdev package dependency on libcurl4-gnutls-dev is manually
While it is easy for build-dependency (just use libcurl4-gnutls-dev |
libcurl3-gnutls-dev), I see a problem here with libdev package
dependency. It should depend not on libcurl4-gnutls-dev |
libcurl3-gnutls-dev, but on exact one that was actually used when
building package.
How to
On Mon, Feb 25, 2008 at 11:48:21PM +0300, Nikita V. Youshchenko wrote:
While it is easy for build-dependency (just use libcurl4-gnutls-dev |
libcurl3-gnutls-dev), I see a problem here with libdev package
dependency. It should depend not on libcurl4-gnutls-dev |
libcurl3-gnutls-dev, but
On Mon, Feb 25, 2008 at 23:48:21 +0300, Nikita V. Youshchenko wrote:
Although not very probably, until now Debian used to support static linking
(libdev packages provide .a files, and depend on libdev packages that
provide dependent .a files).
That's not true, afaik. If you're linking
On Mon, Feb 25, 2008 at 11:48:21PM +0300, Nikita V. Youshchenko wrote:
While it is easy for build-dependency (just use
libcurl4-gnutls-dev | libcurl3-gnutls-dev), I see a problem here
with libdev package dependency. It should depend not on
libcurl4-gnutls-dev |
On Mon, Feb 25, 2008 at 10:56:09PM +0300, Nikita V. Youshchenko wrote:
I maintain libetpan package, which build-depends on libcurl4-gnutls-dev.
Resulting library package dependency is calculated using
${shlib:Depends}, however libdev package dependency on
libcurl4-gnutls-dev is manually
Nikita V. Youshchenko wrote:
Hi
I maintain libetpan package, which build-depends on libcurl4-gnutls-dev.
Resulting library package dependency is calculated using ${shlib:Depends},
however libdev package dependency on libcurl4-gnutls-dev is manually
written in debian/control file. The
On Tue, Feb 26, 2008 at 12:11:05AM +0300, Nikita V. Youshchenko wrote:
While it is easy for build-dependency (just use libcurl4-gnutls-dev |
libcurl3-gnutls-dev), I see a problem here with libdev package
dependency. It should depend not on libcurl4-gnutls-dev |
libcurl3-gnutls-dev, but on
On Mon, Feb 25, 2008 at 11:48:21PM +0300, Nikita V. Youshchenko wrote:
While it is easy for build-dependency (just use libcurl4-gnutls-dev |
libcurl3-gnutls-dev), I see a problem here with libdev package
dependency. It should depend not on libcurl4-gnutls-dev |
libcurl3-gnutls-dev, but
Roger Leigh [EMAIL PROTECTED] writes:
I stopped providing static libraries in all my library packages quite a
while back. No one used them, and they were just needless bloat. I
can't say I would be upset if we dropped all the static libraries from
the entire archive--is there actually a
On Mon, Feb 25, 2008 at 09:53:37PM +0100, Julien Cristau wrote:
On Mon, Feb 25, 2008 at 23:48:21 +0300, Nikita V. Youshchenko wrote:
Although not very probably, until now Debian used to support static linking
(libdev packages provide .a files, and depend on libdev packages that
provide
21 matches
Mail list logo
