how can include other my own serperat file in .deb package file so that
after when package will be insgtalled that file go to my specified
location.where should i specify that file and its location..in
debain pakcage
Thanks
On Fri, 28 Feb 2003, Sheraz Khan wrote:
how can include other my own serperat file in .deb package file so that
after when package will be insgtalled that file go to my specified
location.where should i specify that file and its location..in
debain pakcage
If you're trying
On Fri, Feb 28, 2003 at 07:57:02PM +1100, Matthew Palmer wrote:
* Add your file to the package somewhere
You should put it in the debian/ directory. If its a binary file, you
have to uuencode it (to make diff happy) and on install uudecode it.
There is a perl script attached for this.
Cheers,
-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
-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
use
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 lower
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.developers for
-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
Hi.
OpenEXR is about to release a new version, but upstream wants a bit of
mass--checking before that happens.
I am (have already) building a new package from the cvs tree, but my question
is:
Shall I run the autobuild (called bootstrap) on my system and go with the
package using those results
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 28, 2003 at 07:02:05PM +0100, Michel Dnzer 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 another
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
come
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 tested it
makepp is a drop-in replacement for GNU make which has a number of
features that allow for more reliable builds and simpler build
files. It supports almost all of the syntax that GNU make supports,
and can be used with makefiles produced by utilities such as
automake. It is called makepp (or
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 using
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.. help the
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 you have
Hi mentors,
I'm looking for information about debian developer/maintainer.
I read in debian page that the only way to became maintainer is developing some nice
program, but I have two friends that are only who make the .deb package.
The situation is: I don't have a nice package develped by me,
Hello:
I'd like to request for someone to sponsor the following unofficial
packages I have: snes9express (1.39-beta) - a GUI frontend for SNES9x
(as far as I know this is still an orphaned package); and visualboy
advance (a gameboy/gameboy color/gameboy advance emulator for Linux).
The said
how can include other my own serperat file in .deb package file so that
after when package will be insgtalled that file go to my specified
location.where should i specify that file and its location..in
debain pakcage
Thanks
On Fri, 28 Feb 2003, Sheraz Khan wrote:
how can include other my own serperat file in .deb package file so that
after when package will be insgtalled that file go to my specified
location.where should i specify that file and its location..in
debain pakcage
If you're trying
On Fri, Feb 28, 2003 at 07:57:02PM +1100, Matthew Palmer wrote:
* Add your file to the package somewhere
You should put it in the debian/ directory. If its a binary file, you
have to uuencode it (to make diff happy) and on install uudecode it.
There is a perl script attached for this.
Cheers,
-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
-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
use
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 lower
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.developers for
-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
Hi.
OpenEXR is about to release a new version, but upstream wants a bit of
mass--checking before that happens.
I am (have already) building a new package from the cvs tree, but my question
is:
Shall I run the autobuild (called bootstrap) on my system and go with the
package using those results
-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 another
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
come
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 tested it
-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 answer: don't
makepp is a drop-in replacement for GNU make which has a number of
features that allow for more reliable builds and simpler build
files. It supports almost all of the syntax that GNU make supports,
and can be used with makefiles produced by utilities such as
automake. It is called makepp (or
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 using
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.. help the
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 you have
35 matches
Mail list logo
