On Fri, 16 Sep 2005 23:24:39 +0000, Rodrigo Lazo wrote:

> Well, thanks all of you for your replies. I did rebuild the package
> using quickpkg but it didn't fix the problem, the only way I found to
> do it was compiling it on the second computer. That fix it but it
> wouldn't be an alternative if somebody find this problem and have
> twenty machines to install. What else could be done?

Do you see the same problem if you install on the first machine with
--buildpkg instead of creating the package post-install with quickpkg.
There could be a bug in quickpkg.

In you situation, I would add buildpkg to FEATURES, to have packages
built automatically. This has the further advantage that emerge does this
by compiling the source, building the package and then installing from
the binary package, so any problems will show up at build time rather
than waiting to bite you later.


-- 
Neil Bothwick

Those are my principles. If you don't like them I have others.

Attachment: pgpPqsXMfMCgJ.pgp
Description: PGP signature

Reply via email to