On Thursday 20 January 2005 00:33, Chris Gianelloni wrote: > 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.
well, until now basc also requires to copy the emerge.log, but this breaks the 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. can you tell me, how this should look like in the ebuild, before I again get flamed because I've released an ebuild which is against all policies or whatever...? > > 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. >[...] -- http://de.gentoo-wiki.com Alexander Mieland (aka dma147) http://www.gentoo-stats.org Registered Linux-User #249600 http://www.php-programs.de GnuGPG-ID: 27491179 http://www.affen-in-not.de www.php-programs.de/dma147.asc
pgpOd8DCAbpo9.pgp
Description: PGP signature
