Re: Injecting versions of build-deps in the deps

2007-12-09 Thread Raphael Hertzog
On Fri, 07 Dec 2007, Loïc Minier wrote: > On Fri, Dec 07, 2007, Raphael Hertzog wrote: > > libgtk-x11-2.0.so.0 libgtk2.0-0 #MINVER# > > * Devel-Package: libgtk2.0-dev > > [EMAIL PROTECTED] 2.8.0 > > ... > > How does that sound ? > > Sounds like a good start! Perhaps the injection should be exp

Re: Injecting versions of build-deps in the deps

2007-12-07 Thread Loïc Minier
On Fri, Dec 07, 2007, Raphael Hertzog wrote: > libgtk-x11-2.0.so.0 libgtk2.0-0 #MINVER# > * Devel-Package: libgtk2.0-dev > [EMAIL PROTECTED] 2.8.0 > ... > How does that sound ? Sounds like a good start! Perhaps the injection should be explicitely requested with: * UseBuildDepVersionAsMinVer

Re: Injecting versions of build-deps in the deps

2007-12-07 Thread Raphael Hertzog
On Fri, 07 Dec 2007, Loïc Minier wrote: > I do imagine it wont be mandatory (or useful) for all libs as well and > I agree it should be added on a per package basis; one idea I > mentionned to Raphaël is to extend the shlibs / symbols system to allow > a syntax meaning "Take the build-dep versi

Re: Injecting versions of build-deps in the deps

2007-12-07 Thread Loïc Minier
On Fri, Dec 07, 2007, Colin Watson wrote: > I wonder if the objections raised to this suggestion could be addressed > by making it optional in some way - perhaps either by requiring it to be > manually enabled for each library by some kind of shlibs/symbols-like > system, or by providing support fo

Re: Injecting versions of build-deps in the deps

2007-12-07 Thread Colin Watson
On Mon, Dec 03, 2007 at 06:38:20PM +0100, Julien Cristau wrote: > On Mon, Dec 3, 2007 at 17:33:41 +0100, Josselin Mouette wrote: > > Every successful call to pkg-config would fill in a file, let’s say > > debian/pkgconfig.deps, that would in the end contain: > > > > # pkgconfig_file requi

Re: Injecting versions of build-deps in the deps

2007-12-03 Thread Mike Hommey
On Mon, Dec 03, 2007 at 05:36:43PM +0100, Josselin Mouette wrote: > Le dimanche 02 décembre 2007 à 19:35 +0100, Mike Hommey a écrit : > > I think there is a problem using build dependencies for that purpose: > > There are dozens of reasons why you want to build-depend on libfoo-dev > > >= version t

Re: Injecting versions of build-deps in the deps

2007-12-03 Thread Julien Cristau
On Mon, Dec 3, 2007 at 17:33:41 +0100, Josselin Mouette wrote: > Every successful call to pkg-config would fill in a file, let’s say > debian/pkgconfig.deps, that would in the end contain: > > # pkgconfig_file required_version dev_package shared_package > version > x11 1.

Re: Injecting versions of build-deps in the deps

2007-12-03 Thread Josselin Mouette
Le dimanche 02 décembre 2007 à 19:35 +0100, Mike Hommey a écrit : > I think there is a problem using build dependencies for that purpose: > There are dozens of reasons why you want to build-depend on libfoo-dev > >= version that do NOT involve working around bugs in the library at > runtime. There

Re: Injecting versions of build-deps in the deps

2007-12-03 Thread Josselin Mouette
Hi, Le dimanche 02 décembre 2007 à 17:11 +0100, Loïc Minier a écrit : > An idea that came up is to use a per-dependent package information > provided by the maintainer such as the build-deps version [2]. It > would require a map from deps to build-deps and could typically be > combined with t

Re: Injecting versions of build-deps in the deps

2007-12-03 Thread Loïc Minier
On Sun, Dec 02, 2007, Mike Hommey wrote: > I think there is a problem using build dependencies for that purpose: > There are dozens of reasons why you want to build-depend on libfoo-dev > >= version that do NOT involve working around bugs in the library at > runtime. There are so many that it would

Re: Injecting versions of build-deps in the deps

2007-12-02 Thread Raphael Hertzog
On Sun, 02 Dec 2007, Mike Hommey wrote: > On Sun, Dec 02, 2007 at 05:11:52PM +0100, Loïc Minier wrote: > > What do you think of such a system? Please share your ideas and > > comments! > > I think there is a problem using build dependencies for that purpose: > There are dozens of reasons why yo

Re: Injecting versions of build-deps in the deps

2007-12-02 Thread Mike Hommey
On Sun, Dec 02, 2007 at 05:11:52PM +0100, Loïc Minier wrote: > What do you think of such a system? Please share your ideas and > comments! I think there is a problem using build dependencies for that purpose: There are dozens of reasons why you want to build-depend on libfoo-dev >= version that

Re: Injecting versions of build-deps in the deps

2007-12-02 Thread Loïc Minier
On Sun, Dec 02, 2007, Kurt Roeckx wrote: > > An example would be package foobar3 build-depending on libfoo3 (>= > > 2.10.2). When built against libfoo3 2.12.0-2 which provides a symbols > > file, the resulting binaries need symbols from libfoo3 (>= 2.8.7) (as > > the symbols file say), the new

Re: Injecting versions of build-deps in the deps

2007-12-02 Thread Kurt Roeckx
On Sun, Dec 02, 2007 at 05:11:52PM +0100, Loïc Minier wrote: > > An example would be package foobar3 build-depending on libfoo3 (>= > 2.10.2). When built against libfoo3 2.12.0-2 which provides a symbols > file, the resulting binaries need symbols from libfoo3 (>= 2.8.7) (as > the symbols fil