Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Junichi Uekawa
> Lintian, however, can't know that this particular library usually is > preloaded, not linked to. Hence the override. If its use is going to be something like that, please don't put it in /usr/lib. That's what the lintian warning is about. regards, junichi -- To UNSUBSCRIBE, emai

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Junichi Uekawa
> Lintian, however, can't know that this particular library usually is > preloaded, not linked to. Hence the override. If its use is going to be something like that, please don't put it in /usr/lib. That's what the lintian warning is about. regards, junichi -- To UNSUBSCRIBE, emai

Re: Need help: difficult NM / requestor

2003-07-25 Thread Eray Ozkural
Hi there, Thanks Roland for presenting the situation objectively. He has taken time to elaborate on what led to the current undesirable situation and our IRC discussion today. It is as he has said. I didn't see any significant misrepresentation. [*] I am very busy writing a paper and doing a b

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Matthias Urlichs
Hi, Colin Watson wrote: > On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote: >> My personal preference is to add a Lintian override, and leave it at >> that. > > But the error says that it isn't a shared library at all, which is > equally applicable to LD_PRELOADed libraries. The r

Re: Need help: difficult NM / requestor

2003-07-25 Thread Eray Ozkural
Hi there, Thanks Roland for presenting the situation objectively. He has taken time to elaborate on what led to the current undesirable situation and our IRC discussion today. It is as he has said. I didn't see any significant misrepresentation. [*] I am very busy writing a paper and doing a b

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Colin Watson
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote: > My personal preference is to add a Lintian override, and leave it at > that. But the error says that it isn't a shared library at all, which is equally applicable to LD_PRELOADed libraries. The right approach is to find out *why*

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Matthias Urlichs
Hi, Colin Watson wrote: > On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote: >> My personal preference is to add a Lintian override, and leave it at >> that. > > But the error says that it isn't a shared library at all, which is > equally applicable to LD_PRELOADed libraries. The r

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Matthias Urlichs
Hi, Sean 'Shaleh' Perry wrote: > correct, so it does not belong in /usr/lib, it belongs in > /usr/lib/snoopy or some such location. IMHO it doesn't make much sense to create a subdirectory for a single file. Besides, when developing sometimes you _do_ want to link to this shared library. (I've do

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Colin Watson
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote: > My personal preference is to add a Lintian override, and leave it at > that. But the error says that it isn't a shared library at all, which is equally applicable to LD_PRELOADed libraries. The right approach is to find out *why*

Re: Need help: difficult NM / requestor

2003-07-25 Thread Richard A. Hecker
On Thu, Jul 24, 2003 at 06:25:55PM +0200, Roland Mas wrote: > .. > > So he showed up on IRC today, demanded to talk to elmo (who didn't > answer), started to be not-quite-rude-but-still-not-very-smooth to > people present, and stated a few things that really got the heat > started. Namely,

Re: lintian W: sharedobject-in-library-directory-not-actually-a-shlib

2003-07-25 Thread Matthias Urlichs
Hi, Sean 'Shaleh' Perry wrote: > correct, so it does not belong in /usr/lib, it belongs in > /usr/lib/snoopy or some such location. IMHO it doesn't make much sense to create a subdirectory for a single file. Besides, when developing sometimes you _do_ want to link to this shared library. (I've do

Re: ITA: yadex -- WAD file editor for doom-style WADs

2003-07-25 Thread Roland Mas
Frederic Wagner (2003-07-25 15:33:31 +0200) : > I'd like to maintain yadex, which I'm using quite often, for debian. > Anyway it was about time for me to do something for debian, so > adopting an existing package should be the right way to start. > > I've packaged it, changed changelog, and closed

Re: Need help: difficult NM / requestor

2003-07-25 Thread Richard A. Hecker
On Thu, Jul 24, 2003 at 06:25:55PM +0200, Roland Mas wrote: > .. > > So he showed up on IRC today, demanded to talk to elmo (who didn't > answer), started to be not-quite-rude-but-still-not-very-smooth to > people present, and stated a few things that really got the heat > started. Namely,

ITA: yadex -- WAD file editor for doom-style WADs

2003-07-25 Thread Frederic Wagner
retitle 201391 ITA: yadex -- WAD file editor for doom-style WADs stop Hi, I'd like to maintain yadex, which I'm using quite often, for debian. Anyway it was about time for me to do something for debian, so adopting an existing package should be the right way to start. I've packaged it, changed c

Re: ITA: yadex -- WAD file editor for doom-style WADs

2003-07-25 Thread Roland Mas
Frederic Wagner (2003-07-25 15:33:31 +0200) : > I'd like to maintain yadex, which I'm using quite often, for debian. > Anyway it was about time for me to do something for debian, so > adopting an existing package should be the right way to start. > > I've packaged it, changed changelog, and closed

ITA: yadex -- WAD file editor for doom-style WADs

2003-07-25 Thread Frederic Wagner
retitle 201391 ITA: yadex -- WAD file editor for doom-style WADs stop Hi, I'd like to maintain yadex, which I'm using quite often, for debian. Anyway it was about time for me to do something for debian, so adopting an existing package should be the right way to start. I've packaged it, changed c