Re: [gentoo-dev] writing ebuild scripts

[Karl Trygve Kalleberg <karltk@prosalg.no>]

On 08 Mar 2002 03:43:13 +0100
Erik Grinaker <erikg@wired-networks.net> wrote:

> - What is the best way to determine dependencies for a file, and how
> important is it to have minimum version info for dependencies? Unless I
> find any info in the docs, would common sense and a quick peek at
> configure-scripts/makefiles ot the source suffice?

Yes. If all else fails, you could just default to the version you're
actually building it against. It is very unlikely that we'll add older
versions to the tree anyway.

> - What is the best way to install built files? Using make install or
> using the dobin/doman/whatever scripts? ...which brings me on to the
> next question ;

make install is preferrable. Make certain that it actually installs into
${D} at this stage, by either adding DESTDIR=${D} or prefix=${D}/usr,
depending on which alternative the make files support. 
> - Is there any database over what files belong to what package?

Yes, /var/db/pkg contains a lot of neat info. Look at each packages
CONTENTS file. The qpkg tool in gentoolkit is a nice, quick frontend to
much of the info in /var/db/pkg.

> - Do you have any policies for testing? Is it enough that I test the
> package on my own system, or should I have a clean installation (via
> chroot, usermode linux, dualboot or whatever) I can use for testing?

It is sufficient that it works on your installation. If you know you have
done something horribly weird to your install, let another Gentoo user
test it too.

In time, all ebuilds will be tested on our Tinderbox before being put into
the stable tree.

> - Should I work against cvs or the Bugzilla?

Not quite certain what you mean by this. Submit ebuilds through bugzilla,
preferrably as plain-text attachments to the enhancement request you're
filing. emerge rsync gives you exactly what's in CVS now (albeit with a
time-delay of a few minutes).

Kind regards,

Karl T