Hi,
On Sun, Dec 02, 2007 at 09:08:54PM +0100, Holger Levsen wrote:
On Sunday 02 December 2007 13:19, Patrick Schoenfeld wrote:
Really, it may have sounded more rude to you, then it was meant to be.
But I was really annoyed by such a statement,
That rather implies you were unfriendly, at
Hi,
Il giorno lun, 03/12/2007 alle 04.38 +0100, Leo costela Antunes ha
scritto:
Francesco Namuri wrote:
I would like to know, what in your opinion is the best solution.
And then, I am mistaken thinking that the problem is related to the fact
that lib64/ is a symlink to lib/ ?
I'm I
Hi,
Il giorno lun, 03/12/2007 alle 01.00 -0300, Felipe Sateler ha scritto:
Leo costela Antunes wrote:
could implement something like the widely used
AC_RELOCATABLE macro to his scripts, to make a '--disable-rpath' option
available at configure time.
Is this really needed? Most
Dear Mentors;
Can someone point me to policy about file headers? I am currently
looking at a package with a GPL copyright file in the top directory,
and a terse statment copyright X, released under the GPL in most,
but not all files. I think the files without copyright are
non-essential, and
On Sun, Dec 02, 2007 at 09:08:54PM +0100, Holger Levsen wrote:
Hi,
On Sunday 02 December 2007 13:19, Patrick Schoenfeld wrote:
Thats bad. You should not answer to such questions if you don't know it
for your self! Thats especially true because of your DD status that
causes others
2007/12/2, Patrick Schoenfeld [EMAIL PROTECTED]:
1) Copyright / license issues: By removing important information from
the previous packaging you might insult the packaging license.
Redistribution in Debian might therefore be illegal.
While I do believe that, as a general rule, it's much
David Bremner [EMAIL PROTECTED] writes:
Can someone point me to policy about file headers? I am currently
looking at a package with a GPL copyright file in the top directory, and
a terse statment copyright X, released under the GPL in most, but not
all files. I think the files without
Francesco Namuri [EMAIL PROTECTED] writes:
I'm thinking this because after the call of ./configure the generated
libtool file contains all the lib variables set to corresponding lib64
directory eg (after a call of ./configure):
Yeah, that's broken, don't do that. /usr/lib is the library path
8 matches
Mail list logo
