On Thu, Feb 15, 2001 at 12:43:45PM -0500, Jimmy Kaplowitz wrote:
> Hi. I have decided (and gotten permission) to package NISCA, which is a
> program
> that is similar to but more customizable than MRTG. It is written in php, so
> there are no compiled files.
Thus all files are architecture indepe
On Fri, Feb 16, 2001 at 12:15:12AM +0100, Martin Albert wrote:
> -- Would that be 'legal' anyway? Modifiying installed files of one pkg
> by the scripts of another? (They're closely related however and chances
> are good that after all this weird stuff, the next pkg to be removed
> would be the
On Thu, Feb 15, 2001 at 12:43:45PM -0500, Jimmy Kaplowitz wrote:
> Hi. I have decided (and gotten permission) to package NISCA, which is a program
> that is similar to but more customizable than MRTG. It is written in php, so
> there are no compiled files.
Thus all files are architecture independ
On Fri, Feb 16, 2001 at 12:15:12AM +0100, Martin Albert wrote:
> -- Would that be 'legal' anyway? Modifiying installed files of one pkg
> by the scripts of another? (They're closely related however and chances
> are good that after all this weird stuff, the next pkg to be removed
> would be the
MoiN
On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> Are there any docs with guidelines on package naming?
See the packaging manual, Section 11.3.
> The build process gives me
> libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0
So your package should be called
MoiN
On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> Are there any docs with guidelines on package naming?
See the packaging manual, Section 11.3.
> The build process gives me
> libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0
So your package should be called
On Thu, Feb 08, 2001 at 02:40:36PM +0100, Domenico Andreoli wrote:
> now reading the packaging manual i found this writing:
>
> "A Conflicts entry should almost never have an `earlier than' version
> clause. This would prevent dpkg from upgrading or installing the package
> which declared such a
On Thu, Feb 08, 2001 at 02:40:36PM +0100, Domenico Andreoli wrote:
> now reading the packaging manual i found this writing:
>
> "A Conflicts entry should almost never have an `earlier than' version
> clause. This would prevent dpkg from upgrading or installing the package
> which declared such
On Wed, Jan 24, 2001 at 02:50:46PM +0100, Christian Hammers wrote:
> I like to build my mysql package with chroot support and therfore jail it
> somewhere under /var/lib/mysql and link the log files to /var/log.
Do you plan to make them officially available in debian?
> I either statically link i
On Wed, Jan 24, 2001 at 02:50:46PM +0100, Christian Hammers wrote:
> I like to build my mysql package with chroot support and therfore jail it
> somewhere under /var/lib/mysql and link the log files to /var/log.
Do you plan to make them officially available in debian?
> I either statically link
On Wed, Jan 03, 2001 at 03:57:39AM -0800, [EMAIL PROTECTED] wrote:
> Is there any guide, hints or example package in order to
> make a package containing perl scripts & perl modules?
> (No compiled sources at all)
In addition to the packagnig manual you should also have a look
at the perl-policy p
On Wed, Jan 03, 2001 at 03:57:39AM -0800, [EMAIL PROTECTED] wrote:
> Is there any guide, hints or example package in order to
> make a package containing perl scripts & perl modules?
> (No compiled sources at all)
In addition to the packagnig manual you should also have a look
at the perl-policy
MoiN
On Sat, Dec 09, 2000 at 03:39:01PM +1100, Jeremy Higgs wrote:
> ok, I have modified the postinst.debhelper script and renamed it
> (saved it as) postinst in the debian directory. I then created the
> deb package.
Please don't do that. The postinst.debhelper script is generated
by debhelper
MoiN
On Sat, Dec 09, 2000 at 02:46:51PM +1100, Jeremy Higgs wrote:
> the man page for update-rc.d didn't say WHERE to execute update-rc.d,
> so I put it at the end.
The update-rc.d has to be executed in the postinst of the
package. If you're using debhelper those scripts should be
generated auto
MoiN
On Sat, Dec 09, 2000 at 03:39:01PM +1100, Jeremy Higgs wrote:
> ok, I have modified the postinst.debhelper script and renamed it
> (saved it as) postinst in the debian directory. I then created the
> deb package.
Please don't do that. The postinst.debhelper script is generated
by debhelpe
MoiN
On Sat, Dec 09, 2000 at 02:46:51PM +1100, Jeremy Higgs wrote:
> the man page for update-rc.d didn't say WHERE to execute update-rc.d,
> so I put it at the end.
The update-rc.d has to be executed in the postinst of the
package. If you're using debhelper those scripts should be
generated aut
MoiN
Just some additional thoughts...
On Thu, Dec 07, 2000 at 01:32:04AM +0100, Manuel Estrada wrote:
> Is there some automated way to keep the .ex files and not include
> them in the source package?
Yes. Don't remove the dh-make package, as it keeps the .ex files
in the directory /usr/share/de
MoiN
Just some additional thoughts...
On Thu, Dec 07, 2000 at 01:32:04AM +0100, Manuel Estrada wrote:
> Is there some automated way to keep the .ex files and not include
> them in the source package?
Yes. Don't remove the dh-make package, as it keeps the .ex files
in the directory /usr/share/d
MoiN
On Sat, Nov 25, 2000 at 01:53:40AM +0800, zhaoway wrote:
> i have a basic x application which has an entry in debian menu.
> may i add an entry in gnome menu for it? though it uses no gtk
> but just a plain standard x application.
I don't know, but does the debian menusupport not try to put
MoiN
On Sat, Dec 02, 2000 at 08:28:49AM -0700, tony mancill wrote:
> I'm working on a package for ripperX, which comes in a ripperX_2.0 tarball
> and extracts itself into ripperX-2.0 directory, and produces a "ripperX"
> binary.
>
> When I left things as they were upstream, dh_make doesn't compla
MoiN
On Sat, Nov 25, 2000 at 01:53:40AM +0800, zhaoway wrote:
> i have a basic x application which has an entry in debian menu.
> may i add an entry in gnome menu for it? though it uses no gtk
> but just a plain standard x application.
I don't know, but does the debian menusupport not try to put
MoiN
On Sat, Dec 02, 2000 at 08:28:49AM -0700, tony mancill wrote:
> I'm working on a package for ripperX, which comes in a ripperX_2.0 tarball
> and extracts itself into ripperX-2.0 directory, and produces a "ripperX"
> binary.
>
> When I left things as they were upstream, dh_make doesn't compl
MoiN
On Wed, Nov 15, 2000 at 11:37:50PM -0500, [EMAIL PROTECTED] wrote:
> Hi there,
>
> I'm attempting to packing the OpenIL library (openil.sourceforge.net), and
> I'm running into some problems.
>
> I used dh_make to set up the debian directory for me, I edited the project's
> makefile so that
MoiN
On Wed, Nov 15, 2000 at 11:37:50PM -0500, [EMAIL PROTECTED] wrote:
> Hi there,
>
> I'm attempting to packing the OpenIL library (openil.sourceforge.net), and
> I'm running into some problems.
>
> I used dh_make to set up the debian directory for me, I edited the project's
> makefile so tha
MoiN
On Mon, Nov 06, 2000 at 10:20:07AM +0900, Junichi Uekawa wrote:
> Logically thinking they belong to *-dev packages, or if needed at runtime,
> in lib* packages.
Those *-config scripts I know of are only needed to compile
packages. So they should go into *-dev.
> However some people put it
MoiN
On Mon, Nov 06, 2000 at 10:20:07AM +0900, Junichi Uekawa wrote:
> Logically thinking they belong to *-dev packages, or if needed at runtime,
> in lib* packages.
Those *-config scripts I know of are only needed to compile
packages. So they should go into *-dev.
> However some people put it
26 matches
Mail list logo
