From: Marko Mikulicic <marko@seul.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] doinst recursive?
Date: Tue, 04 Jun 2002 16:41:54 +0200 [thread overview]
Message-ID: <3CFCD1B2.90305@seul.org> (raw)
In-Reply-To: 1023200546.12194.25.camel@red.ces.clemson.edu
Grant Goodyear wrote:
>>I was wondering if switching to CVS would only update the ebuilds or
>>also update (relax) the maskings. In other words, it is safe to
>> sync the portage tree with gentoo cvs ?
>
>
> Yep. The anoncvs and rsync servers return exactly the same files.
So, if I did emerge rsync and the acroread bug was still there,
the bug was obviously not fixed (or I didn't get the last release).
The bug fixes should differ in -r? .
The revision I have is acroread-5.05-r3.ebuild.
It contains the following code snippet:
for i in Browsers Reader Resource
do
insinto ${INSTALLDIR}
doins ${i}/*
done
It should copy recursively the Browser, Reader and Resource
subdirectories in ${INSTALLDIR}, but instead a warning is issued.
(reasonable, since it uses "/bin/install" and it doesn't copy recursively).
I have fixed it adding:
cp -r Browsers Reader Resource ${D}/${INSTALLDIR}
just below.
Can you explain me why is preferred to use doins instead of cp ...
${D}/${INSTALLDIR}? If I have sources of a package it is safe to use a
"emake install" (configuring it previously with something like
--prefix=${D}/usr) ?
next prev parent reply other threads:[~2002-06-04 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 12:06 [gentoo-dev] doinst recursive? Marko Mikulicic
2002-06-04 12:21 ` Dan Naumov
2002-06-04 12:42 ` Marko Mikulicic
2002-06-04 13:08 ` Paul de Vrieze
2002-06-04 13:45 ` Marko Mikulicic
2002-06-04 14:00 ` Dan Naumov
2002-06-04 14:16 ` Marko Mikulicic
2002-06-04 14:22 ` Grant Goodyear
2002-06-04 14:41 ` Marko Mikulicic [this message]
2002-06-04 14:46 ` Marko Mikulicic
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=3CFCD1B2.90305@seul.org \
--to=marko@seul.org \
--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