On Wed, 2005-01-19 at 23:47 +0100, Alexander Mieland wrote: > if I understand the policies and some devs correctly, this would also be > not good, to make this all in the basc-ebuild. Or am I wrong?
If your application requires it, then I don't see how it would be breaking any policies. Personally, I would have the compile done in a pkg_config function and have the ebuild simply display whether the function needed to be run or not based on the existence of the file. > And btw, I don't want to install this reference-package then (bash in > this case). It only should be a benchmark to get an accourate > compiletime which depends on the power of the used machine. Then don't install it. You can have the ebuild do pretty much whatever you want, you know. > what speaks against it to let the client do this by himself? Perhaps > in /var/tmp, /var/cache or in /usr/share...? Just use a pkg_config for it. That way it could use portage variables like PORTAGE_TMPDIR to determine where to do its work, or even use /tmp and clean up after itself. > Another question: > What's about 64bit machines or sparc, mips, ppc's, ...? > Would bash compile on these arches without problems or is there a special > version of bash needed? Bash works on all platforms that Gentoo does. -- Chris Gianelloni Release Engineering - Operational/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
