Re: ITP vexim

[Justin Pryzby <justinpryzby@users.sourceforge.net>]

On Sun, Jan 22, 2006 at 05:22:46PM +0100, Daniel Knabl wrote:
> Hi there,
> 
> as i use this piece of software already on my own host, i would like to
> provide it to any other users.
> 
> for the first steps i have created a directory "vexim-2.2.rc1". it
> includes all of the used files (most are *.php files). next i did
> "dh_make" on it.
> as i think it is a single binary i have coosen this.
Single binary means "creating only 1 .deb", which is typical.  It
isn't talking about "only 1 thing in /usr/bin/".

> if there is anyone willing and/or able to help me with the next steps i
> would be very happy. right now i have some questions on how to get
> debconf and templates working,
Read debconf-devel(7), and google about the config, templates and
postinst files WRT debconf.

> so that the user can interact whilest
> installing. this would be very important - however i do not really know,
> how to get the user's input and how to process it further. i think
> about cryptic postinst script using many lines containing sed
> s/@bla@/$user_in/ > $tempfile ...
Are you planning on providing fully generalized "maintainer script"
handling of the config files, or are conffiles sufficient?

> but first of all i would need some help on the control-file, the
> rules-file and on "how to resolve dependencies" of my package.
Ok what about?

> anyone willing to help: have a look at http://knabl.com/~daniel/vexim
Please make the .diff.gz available, and preferrably in such a way that
lynx will view it instead of asking how to save it..

You can't just overwrite exim4-config's conffiles.  I *think* you can
Provide: exim4-config, but only if you also Conflict: exim4-config.
You'll have to handle transferring of conffiles ownership gracefully,
which is something apparently nobody does.

Do you intend to Depend: exim4?

How do you deal with the exim4 "conf.d" model vs the exim4.conf model?

Your rules file doesn't function at all with dpkg-buildpackage or any
other Debian tools :)

sed -i -e 's/virtuel/virtual/; s/configuratin/configuration/;' ./debian/control

Standards-Version: 2.2.rc1

That doesn't mean what you think it does :)  It is a version of Debian
policy document, not of your package.

-- 
Clear skies,
Justin