On Fri, Feb 28, 2003 at 11:38:33PM -0500, Joey Hess wrote:
> Bastian Kleineidam wrote:
> > > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> > I like to have the original .tar.gz exactly as I downloaded it. dh_make
> > unpacks the source and repacks it to a new .orig.tar.gz
On Fri, Feb 28, 2003 at 11:38:33PM -0500, Joey Hess wrote:
> Bastian Kleineidam wrote:
> > > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> > I like to have the original .tar.gz exactly as I downloaded it. dh_make
> > unpacks the source and repacks it to a new .orig.tar.gz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 11:38:33PM -0500, Joey Hess wrote:
> Bastian Kleineidam wrote:
> > > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> > I like to have the original .tar.gz exactly as I downloaded it. dh_make
> > unpacks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 11:38:33PM -0500, Joey Hess wrote:
> Bastian Kleineidam wrote:
> > > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> > I like to have the original .tar.gz exactly as I downloaded it. dh_make
> > unpacks
On Fri, Feb 28, 2003 at 11:42:37PM -0500, Joey Hess wrote:
> You should really ask Russell Coker on -devel. There may well be a
> policy to limit postinst scripts to the things that postinst scripts
> typically do.
Thanks I shall.
I was thinking was that a postinst script, or package inst
Steve Kemp wrote:
> As an aside I wonder how well SE-Linux, or the other improved
> security patches handle installation issues? I know that by installing
> a random package you're effectively giving the package maintainer
> root upon your box.
>
> I'd imagine that a package installation p
Bastian Kleineidam wrote:
> > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> I like to have the original .tar.gz exactly as I downloaded it. dh_make
> unpacks the source and repacks it to a new .orig.tar.gz.
Why would dh_make go out of its way to violate best practices li
On Fri, Feb 28, 2003 at 11:42:37PM -0500, Joey Hess wrote:
> You should really ask Russell Coker on -devel. There may well be a
> policy to limit postinst scripts to the things that postinst scripts
> typically do.
Thanks I shall.
I was thinking was that a postinst script, or package inst
Steve Kemp wrote:
> As an aside I wonder how well SE-Linux, or the other improved
> security patches handle installation issues? I know that by installing
> a random package you're effectively giving the package maintainer
> root upon your box.
>
> I'd imagine that a package installation p
Bastian Kleineidam wrote:
> > Hmm, dh_make is trying to do a similar approach. Why not use that way?
> I like to have the original .tar.gz exactly as I downloaded it. dh_make
> unpacks the source and repacks it to a new .orig.tar.gz.
Why would dh_make go out of its way to violate best practices li
On Fri, 28 Feb 2003, Michel Dänzer wrote:
> On Fre, 2003-02-28 at 18:08, Fabio Massimo Di Nitto wrote:
> >
> > I would also add something about dependencies. Be sure to build always
> > againt the main debian archive and in the worst case with pkgs that are in
> > your external archive of which yo
On Fri, 28 Feb 2003, Steve Kemp wrote:
> On Fri, Feb 28, 2003 at 06:08:23PM +0100, Fabio Massimo Di Nitto wrote:
>
> > BTW never forget that external archive can be as dangerous as usefull.
> > Warn ALWAYS the user that is not an official repository and don't use it
> > only for your own "glory"..
Bastian Kleineidam wrote:
> On Fri, Feb 28, 2003 at 08:19:51PM +0100, Henning Moll wrote:
> > In addition i have some questions to the Depends section in
> > debian/control: ${shlibs:Depends} is a nice feature, but i think
> > for many packages/libraries it is way to strict, because it's
> > always
On Fri, 28 Feb 2003, Michel Dänzer wrote:
> On Fre, 2003-02-28 at 18:08, Fabio Massimo Di Nitto wrote:
> >
> > I would also add something about dependencies. Be sure to build always
> > againt the main debian archive and in the worst case with pkgs that are in
> > your external archive of which yo
On Fri, 28 Feb 2003, Steve Kemp wrote:
> On Fri, Feb 28, 2003 at 06:08:23PM +0100, Fabio Massimo Di Nitto wrote:
>
> > BTW never forget that external archive can be as dangerous as usefull.
> > Warn ALWAYS the user that is not an official repository and don't use it
> > only for your own "glory"..
Bastian Kleineidam wrote:
> On Fri, Feb 28, 2003 at 08:19:51PM +0100, Henning Moll wrote:
> > In addition i have some questions to the Depends section in
> > debian/control: ${shlibs:Depends} is a nice feature, but i think
> > for many packages/libraries it is way to strict, because it's
> > always
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 08:19:51PM +0100, Henning Moll wrote:
> Thanks for you tips! But still some questions remain:
>
> On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> > Native Package or not?
> > --
> > Short answe
On Fri, Feb 28, 2003 at 08:57:18PM +0100, Bastian Kleineidam wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dänzer wrote:
> > I have found pbuilder to be a great way to avoid this as well as other
> > build time side effects.
> I teste
On Fri, Feb 28, 2003 at 06:08:23PM +0100, Fabio Massimo Di Nitto wrote:
> BTW never forget that external archive can be as dangerous as usefull.
> Warn ALWAYS the user that is not an official repository and don't use it
> only for your own "glory".. help the official maintainer with what it will
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dänzer wrote:
> I have found pbuilder to be a great way to avoid this as well as other
> build time side effects.
I tested it several weeks ago and it did not work for me. Perhaps I
should give it anothe
-BEGIN PGP SIGNED MESSAGE-
Thanks for you tips! But still some questions remain:
On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> Native Package or not?
> --
> Short answer: don't make a native package.
Can you explain 'native package'? Did you mean 'bina
On Fri, Feb 28, 2003 at 04:33:47PM +0100, Bastian Kleineidam wrote:
> Bug reports
> ---
> The standard tool for reporting bugs is "reportbug".
> Your package should have:
> File /usr/share/bug/mypackage/control:
> Send-To: [EMAIL PROTECTED]
>
> See /usr/share/doc/reportbug/README.develope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 08:19:51PM +0100, Henning Moll wrote:
> Thanks for you tips! But still some questions remain:
>
> On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> > Native Package or not?
> > --
> > Short answe
On Fri, Feb 28, 2003 at 08:57:18PM +0100, Bastian Kleineidam wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dänzer wrote:
> > I have found pbuilder to be a great way to avoid this as well as other
> > build time side effects.
> I teste
On Fri, Feb 28, 2003 at 06:08:23PM +0100, Fabio Massimo Di Nitto wrote:
> BTW never forget that external archive can be as dangerous as usefull.
> Warn ALWAYS the user that is not an official repository and don't use it
> only for your own "glory".. help the official maintainer with what it will
>
On Fre, 2003-02-28 at 18:08, Fabio Massimo Di Nitto wrote:
>
> I would also add something about dependencies. Be sure to build always
> againt the main debian archive and in the worst case with pkgs that are in
> your external archive of which you have control of. This should atleast
> ensure a lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dänzer wrote:
> I have found pbuilder to be a great way to avoid this as well as other
> build time side effects.
I tested it several weeks ago and it did not work for me. Perhaps I
should give it anothe
-BEGIN PGP SIGNED MESSAGE-
Thanks for you tips! But still some questions remain:
On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> Native Package or not?
> --
> Short answer: don't make a native package.
Can you explain 'native package'? Did you mean 'bina
On Fri, Feb 28, 2003 at 04:33:47PM +0100, Bastian Kleineidam wrote:
> Bug reports
> ---
> The standard tool for reporting bugs is "reportbug".
> Your package should have:
> File /usr/share/bug/mypackage/control:
> Send-To: [EMAIL PROTECTED]
>
> See /usr/share/doc/reportbug/README.develope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, 28 Feb 2003, Bastian Kleineidam wrote:
> Hi,
>
> here are some of my tips when packaging unofficial software as .debs.
> Perhaps its useful for someone :)
>
[SNIP]
> If there is already an official package eg with version "1.1-4", then
On Fre, 2003-02-28 at 18:08, Fabio Massimo Di Nitto wrote:
>
> I would also add something about dependencies. Be sure to build always
> againt the main debian archive and in the worst case with pkgs that are in
> your external archive of which you have control of. This should atleast
> ensure a lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
here are some of my tips when packaging unofficial software as .debs.
Perhaps its useful for someone :)
Packaging tips for unofficial packages
==
Maintainer email
-
You can set the DEBEMAIL en
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, 28 Feb 2003, Bastian Kleineidam wrote:
> Hi,
>
> here are some of my tips when packaging unofficial software as .debs.
> Perhaps its useful for someone :)
>
[SNIP]
> If there is already an official package eg with version "1.1-4", then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
here are some of my tips when packaging unofficial software as .debs.
Perhaps its useful for someone :)
Packaging tips for unofficial packages
==
Maintainer email
-
You can set the DEBEMAIL en
34 matches
Mail list logo
