Re: Questions about packaging a python script

That's quite a lot of detail :) Perhaps this should all be written down somewhere and become the Python Subpolicy? We already have such subpolicies for emacs and menu files and probably some that I forgot. It could be distributed in the python package and referenced from debian-policy. Richard

Re: Questions about packaging a python script

-BEGIN PGP SIGNED MESSAGE- Sudhakar Chandrasekharan <[EMAIL PROTECTED]> writes: > 1. linbot.py and associated *.py files need to be installed in the same > directory. I was thinking of installing these under /usr/lib/linbot/ > Is this the Right Thing to do? Hmm. How about /usr/lib/pyth

Re: Creating two packages from one source

Hi, >>"Peter" == Peter S Galbraith <[EMAIL PROTECTED]> writes: Peter> Can a single rules files be used to make two binary packages from Peter> one orig.tar.gz. Sure. You can look at rules files in the examples in http://master.debian.org/%7Esrivasta/ Look at the rules file f

Questions about packaging a python script

I am in the process of packaging linbot - a python script to do link verification. I have a few questions - 1. linbot.py and associated *.py files need to be installed in the same directory. I was thinking of installing these under /usr/lib/linbot/ Is this the Right Thing to do? 2. I will ln -

Re: Creating two packages from one source

> "Peter" == Peter S Galbraith <[EMAIL PROTECTED]> writes: Peter> Can a single rules files be used to make two binary Peter> packages from one orig.tar.gz. Sure! Take a look at the debian/rules file from the 'gimp' package -- you can fetch the .orig.tar.gz, .dsc, and .diff.gz from deb

Re: Why is "1" appended to package name?

On Tue, Sep 01, 1998 at 05:27:03PM -0400, Ossama Othman wrote: > Hi, > > When I ran deb-make on my package source, it appended a "1" to the package > name in debian/control, for example. Why does deb-make do this? > > e.g: package is "ace1" instead of "ace" because you told deb-make that

what are the latest debian packaging tools.

Hello, ... i have not followed debian things since some time ago, and am a bit lost on what is exactliy the correct set of tools to use to make debian packages. debhelper ? deb-make dpkg-dev ? its a bit confusing, is there a doc on this somewhere ? Friendly, Sven LUTHER

Creating two packages from one source

Can a single rules files be used to make two binary packages from one orig.tar.gz. I want to make a package that will be upgradable, e.g. _-1_i386.deb and another which would not be (it could live alongside other versions of the same package): _-1_i386.deb The alternative creates two orig.ta

Re: /var/state ?

On Wed 02 Sep 1998, Paul Slootman wrote: > I'm in the process of packaging linpopup (a winpopup lookalike). It I've put an initial version of linpopup in ~paul on master, so if anyone wants to have a look... I've used /var/state, and I don't add anything to smb.conf automatically or ask anything