Re: buildpackage doesn't put compiled files into .deb

On Fri, Oct 27, 2000 at 09:28:47PM -0700, Yves Arrouye wrote: > > Is anyone on the new-maint guide bit? I wouldn't remember offhand if > > DH_COMPAT=1 is deprecated for new packages now. > > Something that is confusing for maintainers new to debhelper and that use > dh_make, is that the new mainta

Re: eggdrop .so plugins

On Wed, Oct 25, 2000 at 02:35:43PM +0200, Simon Richter wrote: > On Wed, 25 Oct 2000, Samuel Hocevar wrote: > >But sometimes this is just not possible at all (-fPIC eats a whole > > register and some assembly routines may use all of them), and there are > > situations where not using -fPIC is

Re: buildpackage doesn't put compiled files into .deb

On Fri, Oct 27, 2000 at 09:28:47PM -0700, Yves Arrouye wrote: > > Is anyone on the new-maint guide bit? I wouldn't remember offhand if > > DH_COMPAT=1 is deprecated for new packages now. > > Something that is confusing for maintainers new to debhelper and that use > dh_make, is that the new maint

Re: eggdrop .so plugins

On Wed, Oct 25, 2000 at 02:35:43PM +0200, Simon Richter wrote: > On Wed, 25 Oct 2000, Samuel Hocevar wrote: > >But sometimes this is just not possible at all (-fPIC eats a whole > > register and some assembly routines may use all of them), and there are > > situations where not using -fPIC is

Depends field if I have number of internal libraries

Hello. I have a source from that I build some library packages and binary one. Binary depends on all the libs I build. What should I put in Depends field for my binary? For now I get number of messages like dpkg-shlibdeps: warning: could not find any packages for (libfoo-1.0.0.so.0) dpkg-shlibde

Wrong permissions

Hi, I'm a DD to be, waiting for the DAM to open my accounts. I want to adopt an orphaned package called crafty, a chess game player. i rebuild a new package since there's a new upstream code. The package installs opening books in /var/lib/crafty. Since the program also "learns" how to play, it r

Depends field if I have number of internal libraries

Hello. I have a source from that I build some library packages and binary one. Binary depends on all the libs I build. What should I put in Depends field for my binary? For now I get number of messages like dpkg-shlibdeps: warning: could not find any packages for (libfoo-1.0.0.so.0) dpkg-shlibd

Wrong permissions

Hi, I'm a DD to be, waiting for the DAM to open my accounts. I want to adopt an orphaned package called crafty, a chess game player. i rebuild a new package since there's a new upstream code. The package installs opening books in /var/lib/crafty. Since the program also "learns" how to play, it

Re: buildpackage doesn't put compiled files into .deb

On Sun, 29 Oct 2000, Britton wrote: > > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If > > DH_COMPAT is 2, then debian/ is > > used. I guess your control file has a single package, bsf? > > Out of curiosity, anyone know why this change? It's pretty obvious I guess, sorr

Re: buildpackage doesn't put compiled files into .deb

On Fri, 27 Oct 2000, Yves Arrouye wrote: > My guess is that your rules file has: > > export DH_COMPAT=2 > > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If > DH_COMPAT is 2, then debian/ is > used. I guess your control file has a single package, bsf? Out of curiosity, a

Re: buildpackage doesn't put compiled files into .deb

On Sun, 29 Oct 2000, Britton wrote: > > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If > > DH_COMPAT is 2, then debian/ is > > used. I guess your control file has a single package, bsf? > > Out of curiosity, anyone know why this change? It's pretty obvious I guess, sor

Re: buildpackage doesn't put compiled files into .deb

On Fri, 27 Oct 2000, Yves Arrouye wrote: > My guess is that your rules file has: > > export DH_COMPAT=2 > > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If > DH_COMPAT is 2, then debian/ is > used. I guess your control file has a single package, bsf? Out of curiosity,