From: Stroller <root@stellar.eclipse.co.uk>
To: Spider <spider@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Time to Stop and Clean
Date: Sat, 15 Nov 2003 17:52:19 +0000 [thread overview]
Message-ID: <74D9E77A-1794-11D8-B61B-000A95795F3E@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20031115161726.10f6a957.spider@gentoo.org>
On Nov 15, 2003, at 3:17 pm, Spider wrote:
>>
>> I think the Leafnode2 eBuild is broken, anyway. It seems to install
>> into /var/lib/spool/news/
>> See <http://bugs.gentoo.org/show_bug.cgi?id=25713> - I have attached a
>>
>> copy of the ebuild which seems to work here.
>>
>
> Proposed version still has theese lines :
>
> cat ${S}/README_FIRST | while read line ;
> do
> einfo $line
> done
Sorry - I wasn't considering this aspect of the ebuild. All I have done
- some months ago - is changed 2 lines of the ebuild to correct the
/var path.
> And when you build packages, you never unpack the source, therefore
> ${S}
> will not reference to any place where README_FIRST is.
>
> do zcat ${ROOT}/usr/share/doc/${P}/README_FIRST.gz instead.
>
>
> And your "mkdir -p" lines are also broken...
> Anyhow, is there a good reason why you create theese in the pkg_ part
> instead of in src_install after you have done the main installation?
None of these are my implementations. I'm ashamed to admit that I don't
really know enough Bash scripting to write ebuilds. I'd just like to
see a good ebuild for this package in the portage tree & modified those
2 lines of the present one.
Stroller.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-11-15 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 0:02 [gentoo-dev] Time to Stop and Clean Spider
2003-11-12 23:46 ` Aron Griffis
2003-11-13 15:16 ` Spider
2003-11-13 15:28 ` Spider
2003-11-13 16:34 ` [gentoo-dev] " sf
2003-11-15 13:16 ` [gentoo-dev] " Stroller
2003-11-15 15:17 ` Spider
2003-11-15 15:46 ` Aron Griffis
2003-11-15 18:46 ` Spider
2003-11-15 17:52 ` Stroller [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=74D9E77A-1794-11D8-B61B-000A95795F3E@stellar.eclipse.co.uk \
--to=root@stellar.eclipse.co.uk \
--cc=gentoo-dev@gentoo.org \
--cc=spider@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