Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Sam Morris
I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a libnemiver-common library. The library is probably not very useful without nemiver itself being installed. Is it ok to avoid splitting out a separate libnemiver-common0 package, and

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Paul Cager
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a libnemiver-common library. The library is probably not very useful without nemiver itself being installed. Is it ok to avoid

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Sam Morris
On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a libnemiver-common library. The library is probably not very useful without

Better to run multiple configure/make cycles or use separate sources?

2007-02-19 Thread Roman Müllenschläder
Hi List! I'm packaging a program which offers different options in using different compile options. My wish is to provide different binary-packages in the end. What should be done? Should I prepare the 'rules' to do different compilations with different 'configures' and separate the files

Rhide package

2007-02-19 Thread Keith
hello, i'm looking for a package to get started on for myself and the only one that i have any knowledge of at all (out of those not currently maintained) the rhide IDE is the only one i can think of. however i'm not exactly sure if i'm checking all the places i should (don't want to step on

Re: Better to run multiple configure/make cycles or use separate sources?

2007-02-19 Thread Justin Pryzby
On Mon, Feb 19, 2007 at 05:53:44PM +0100, Roman Müllenschläder wrote: Hi List! I'm packaging a program which offers different options in using different compile options. My wish is to provide different binary-packages in the end. What should be done? Should I prepare the 'rules' to do

Re: Rhide package

2007-02-19 Thread Justin Pryzby
On Mon, Feb 19, 2007 at 12:28:18PM -0500, Keith wrote: hello, i'm looking for a package to get started on for myself and the only one that i have any knowledge of at all (out of those not currently maintained) the rhide IDE is the only one i can think of. however i'm not exactly sure if

Re: Better to run multiple configure/make cycles or use separate sources?

2007-02-19 Thread Roman Müllenschläder
Am Montag, 19. Februar 2007 schrieb Justin Pryzby: On Mon, Feb 19, 2007 at 05:53:44PM +0100, Roman Müllenschläder wrote: Hi List! I'm packaging a program which offers different options in using different compile options. My wish is to provide different binary-packages in the end.

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Steve Langasek
On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a libnemiver-common library. The library is probably not very useful

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Paul Cager
Sam Morris wrote: On Mon, 2007-02-19 at 18:11 +, Paul Cager wrote: On Mon, February 19, 2007 2:37 pm, Sam Morris wrote: On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version

Re: Better to run multiple configure/make cycles or use separate sources?

2007-02-19 Thread James Westby
On (19/02/07 19:54), Roman Müllenschläder wrote: Let's ask different: I'm able to do differnet compiles and install (using 'make install') the whole program (including pos, themes, docs, binaries, etc.) into subdirs beneath debian .. debian/compiled-version1 debian/compiled-version2

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread James Westby
On (19/02/07 14:37), Sam Morris wrote: On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a libnemiver-common library. The

Re: Better to run multiple configure/make cycles or use separate sources?

2007-02-19 Thread tony mancill
Another thing to realize is that the number of binary .debs generated from a source package is dictated by the contents of debian/control. Each Package: stanza indicates another binary .deb to be generated by the package. (Sorry if that's already been mentioned. I didn't see it, and couldn't

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Justin Pryzby
On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote: On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a new version that has split some of its functionality into a

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Steve Langasek
On Mon, Feb 19, 2007 at 07:36:13PM -0500, Justin Pryzby wrote: On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote: On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote: On Mon, February 19, 2007 1:38 pm, Sam Morris wrote: I am packaging the nemiver debugger, which has a

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Russ Allbery
Justin Pryzby [EMAIL PROTECTED] writes: On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote: No, you should *not* put libraries into subdirectories of /usr/lib unnecessarily. Policy prefers it for this case: 10.2: | Shared object files (often .so files) that are not public

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Justin Pryzby
On Mon, Feb 19, 2007 at 05:03:47PM -0800, Russ Allbery wrote: Justin Pryzby [EMAIL PROTECTED] writes: On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote: No, you should *not* put libraries into subdirectories of /usr/lib unnecessarily. Policy prefers it for this case:

Re: Must a source package's shared libraries always be spit into separate binary packages?

2007-02-19 Thread Russ Allbery
Justin Pryzby [EMAIL PROTECTED] writes: On Mon, Feb 19, 2007 at 05:03:47PM -0800, Russ Allbery wrote: Yes, installing the libraries in /usr/lib. For such packages with libraries without sonames, one should just make something up? If the library is not suitable to being treated like a

i need help with

2007-02-19 Thread FROM FILA
{libglade) i been tying to install for the last month and it's killing me, i get a message that says not installable so i go to problems and that say Aplication package is incompatible with current software but i have the lastest?? can you help me or tell me what am i doing wrong i am new to the

[no subject]

2007-02-19 Thread Deepak Kumar Tripathi
Dear Mentors, First let me introduce myself .i am Deepak Tripathi working with debian since 8 year. Now I have adopt some packages please refer to link below. libqt-perl. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379681 and libperlmenu-perl. My question is I am not a debain developer

Re: your mail

2007-02-19 Thread Kumar Appaiah
On Tue, Feb 20, 2007 at 10:52:51AM +0530, Deepak Kumar Tripathi wrote: Dear Mentors, First let me introduce myself .i am Deepak Tripathi working with debian since 8 year. Now I have adopt some packages please refer to link below. libqt-perl.