On Fri, Apr 08, 2011 at 02:01:33PM -0700, Steve Langasek wrote:
> On Fri, Apr 08, 2011 at 09:51:03PM +0200, Bill Allombert wrote:
> > I already made this comment, but I strongly think it should be normative.
> > Specifically we should mandate that:
>
> > 1) /usr/include/ be added to the default he
On Fri, Apr 08, 2011 at 10:17:20PM +0200, Goswin von Brederlow wrote:
> >> What could be allowed is using the new include paths with a Depends on
> >> the multiarch package even if the package itself is not multiarch.
> > No. multiarch-support declares runtime support for ld.so. It has nothing
On Fri, Apr 08, 2011 at 09:51:03PM +0200, Bill Allombert wrote:
> I already made this comment, but I strongly think it should be normative.
> Specifically we should mandate that:
> 1) /usr/include/ be added to the default hearder search path of
> -gcc.
It seems strange to me that we would mandate
On Fri, 08 Apr 2011 at 21:51:03 +0200, Bill Allombert wrote:
> Requiring the user to pass -I to the compiler should be discouraged.
I disagree: independently of multiarch, many libraries do this deliberately
to allow for parallel-installation, and use pkg-config to give out appropriate
CFLAGS.
Fo
Steve Langasek writes:
> On Fri, Apr 08, 2011 at 07:44:27PM +0200, Goswin von Brederlow wrote:
>> > On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
>
>> >> The Multiarch specification only covers libraries and does not
>> >> specifically deal with include files.
>
>> >> To make multiarch
4/8/2011 16:45:36
Todo propietario de un sitio web sabe que conseguir visitantes para el
mismo es una tarea dura, y difícil, pero importantísima.
El estar bien ubicado en los buscadores es una parte fundamental de la
promoción de cualquier sitio web.
Debido a que pensamos que el tema puede ser
On Sat, Apr 02, 2011 at 01:14:28AM -0700, Steve Langasek wrote:
> Hi there,
>
> On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
>
> > The Multiarch specification only covers libraries and does not
> > specifically deal with include files.
>
> > To make multiarch useful for cross-buildin
On Fri, Apr 08, 2011 at 07:44:27PM +0200, Goswin von Brederlow wrote:
> > On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
> >> The Multiarch specification only covers libraries and does not
> >> specifically deal with include files.
> >> To make multiarch useful for cross-building as wel
On Fri, 08 Apr 2011, Goswin von Brederlow wrote:
> It does not allow them in available though breaking many systems that
> have or in the past had a package with such a version available. At
> least 4 people on irc have run into that problem that I saw already.
It does allow them in available. Tho
Raphael Hertzog writes:
> On Sun, 03 Apr 2011, Russ Allbery wrote:
>> My inclination is to second this, but I want to make sure that we've
>> answered your and Julien's objections first.
>
> And for complete reference, dpkg accepts those version in
> /var/lib/dpkg/status (so that dpkg still works
Steve Langasek writes:
> Hi there,
>
> On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
>
>> The Multiarch specification only covers libraries and does not
>> specifically deal with include files.
>
>> To make multiarch useful for cross-building as well as co-installation of
>> libraries
On Mon, 4 Apr 2011, Carsten Hey wrote:
> upstream_version git1234 could be prefixed with epoch 0 and thus lead to
> the version number 0:git1234-debian_revision. Maybe this could be
Nah. Just drop the leading 'git'.
On Mon, 4 Apr 2011, Raphael Hertzog wrote:
> We have no upstream with such ve
12 matches
Mail list logo
