From: Max Kalika <max@gentoo.org>
To: Ben Calvert <ben@stonehenge-net.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] strange ebuild error
Date: Wed, 13 Aug 2003 20:30:08 -0700 [thread overview]
Message-ID: <2147483647.1060806608@[192.168.26.4]> (raw)
In-Reply-To: <200308132000.35834.ben@stonehenge-net.com>
Quoting Ben Calvert <ben@stonehenge-net.com>:
> Am trying my hand at an ebuild for afterstep-2.00.beta1 and am having the
> following problem when adapting the 1.8.11-r2 file: when trying to
> create the digest, I get the following error:
>
> ben@lorax afterstep $ sudo ebuild afterstep-2.00.beta1.ebuild digest
> Password:
> !!! Name error in 2.00.beta1
> !!! Error: PF is null; exiting.
Call the ebuild afterstep-2.00_beta1.ebuild (notice the underscore instead
of dot). You can convert the underscore to the dot for $SRC_URI and $S
within the ebuild code with something like ${P/_beta/.beta/}.
--mk
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-08-14 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 3:00 [gentoo-dev] strange ebuild error Ben Calvert
2003-08-14 3:08 ` Mike Frysinger
2003-08-14 3:30 ` Max Kalika [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='2147483647.1060806608@[192.168.26.4]' \
--to=max@gentoo.org \
--cc=ben@stonehenge-net.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox