Gentoo Archives: gentoo-dev

From: Erik Grinaker <erikg@××××××××××××××.net>
To: gentoo-dev@g.o
Subject: [gentoo-dev] writing ebuild scripts
Date: Thu, 07 Mar 2002 20:47:09
Message-Id: 1015555393.27924.41.camel@maas.wired
1 Hi
3 First I'd like to extend my respect to the Gentoo developers, I
4 installed Gentoo Linux on one of my workstations yesterday, and I am
5 very impressed so far. If no bad things happen I may even start using it
6 as my primary distro.
8 I am making some ebuild-scripts for a few pieces of software I need to
9 install, and will submit these to the Bugzilla for inclusion in the
10 distro. I am a bit uncertain about how, and under what policies, these
11 scripts should be written.
13 Some of the following questions may be answered in the documentation,
14 but in order to avoid any misunderstandings (and as the documentation
15 seems a bit dated) it's probably better to just ask.
17 - What is the best way to determine dependencies for a file, and how
18 important is it to have minimum version info for dependencies? Unless I
19 find any info in the docs, would common sense and a quick peek at
20 configure-scripts/makefiles ot the source suffice?
22 - What is the best way to install built files? Using make install or
23 using the dobin/doman/whatever scripts? ...which brings me on to the
24 next question ;
26 - Is there any database over what files belong to what package?
28 - Do you have any policies for testing? Is it enough that I test the
29 package on my own system, or should I have a clean installation (via
30 chroot, usermode linux, dualboot or whatever) I can use for testing?
32 - Should I work against cvs or the Bugzilla?
35 --
37 Erik Grinaker
38 Freelance UNIX/Linux systems consultant
40 "Perfection is acheived not when there is nothing more to add, but
41 rather when there is nothing more to take away"
42 - Antoine de Saint-Exupéry


Subject Author
Re: [gentoo-dev] writing ebuild scripts Karl Trygve Kalleberg <karltk@×××××××.no>
Re: [gentoo-dev] writing ebuild scripts Grant Goodyear <goodyea@×××××××.edu>