On Wed, Mar 07, 2007 at 03:06:28PM +0100, Jochen Hebbrecht wrote:

Just one question that is left: what does the "minimal" chroot environment contains? I mean: image you start a build with no files in it, what does is contain? :-) ... I guess glibc ? And stuff like that? Is must be defined somewhere ...

To get a complete list just take at a package (or create one) that does not contain a buildrequires line and look at its build log what is installed to build that package. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."

On Wed, Mar 07, 2007 at 03:23:16PM +0100, Jochen Hebbrecht wrote:

2007/3/7, Robert Schiele :

...

To get a complete list just take at a package (or create one) that does not contain a buildrequires line and look at its build log what is installed to build that package.

Ok, I agree ... That is indeed a possibility, but that means there's no single documentation file that can tell you what it does? :p ...

??? You wanted a list of packages and I told you one way to get it. What documentation do you exactly want to have? What do you mean with "what it does"? If you want to have more precise answers you should ask more precise questions. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."

2007/3/7, Michal Marek :

It's defined /usr/lib/build/configs/$distro.conf in the build package. I don't know what all the fileds exactly mean, but the packages from Preinstall:, Required: and Support: should be the ones that get installed by default. No warranty.

YES! That is wat I needed ;-)! Thnx m8! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Wed, Mar 07, 2007 at 03:46:13PM +0100, Jochen Hebbrecht wrote:

2007/3/7, Michal Marek :

...

It's defined /usr/lib/build/configs/$distro.conf in the build package. I don't know what all the fileds exactly mean, but the packages from Preinstall:, Required: and Support: should be the ones that get installed by default. No warranty.

Hmm, I replied too fast I guess ... ... I need to know what all the fields are. Can somebody explain me?

Sure: Preinstall: <packages> The packages that need to be unpacked for build environment setup. This is basically everything that is needed to get rpm/dpkg running, i.e. glibc and the like. Runscripts: <packages> A subset of the preinstall packages. It describes which packages need to have their postinstall scripts run. Required: <packages> These are the packages that make the "normal" build environment, i.e. stuff like gcc, autoconf, automake and the like. Support: <packages> Convenience packages, like "vim" or "strace". The difference to "Required" is that the automatic rebuild detection does not look at support packages, i.e. you don't get an automatic rebuild if "strace" is changed. This list also includes some "-devel" packages and other subpackages of the "Required" packages to keep the Required list small. (I.e. we don't need both "zlib" and "zlib-devel" in Required because both are built from the same source) That's about all there is to know about the build environment setup. Oh, we also do dependency expansion here, so packages needed because of package dependencies automatically get added to the "Required" list. So, the default package list is Preinstall + Required + Support + packages from dependency expansion. Some words about the other fields: Keep: <packages> We really need those packages. Normally, subpackages of the package that we want to build don't get installed. But even if we want to build the "patch" package, we need a working patch program to apply patches from the specfile. So we have "Keep: patch". The preinstalled packages are automatically added to this list. Prefer: <positive-package> Prefer: -<negative-package> This information is used to break ambiguities. Ignore: <package>:<package> This breaks dependencies for the package expansion step. "Ignore: portmap:syslogd" means that we don't need an installed syslogd if we have to install the portmap package. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Michael, can you add that info to the wiki ? Thanks, -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Mittwoch, 7. März 2007 20:31 schrieb Richard Bos:

Op woensdag 7 maart 2007 16:33, schreef Amilcar do Carmo Lucas:

...

Michael, can you add that info to the wiki ?

We (including Amilcar ;) ) can do that to. The only problem is where to add? Should it be on seperate page, or added to: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to or another one of those: http://en.opensuse.org/Category:Build_Service ?

I've currently added it to http://en.opensuse.org/Build_Service/Tips_and_Tricks#How_is_a_buildenvironme... Feel free to move it away from this site (because it doesn't fit there very well ;-) -- Lars Vogdt Autobuild Team SUSE Linux Products GmbH GF: Markus Rex Nuernberg, Germany HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org