>>>>> On Thu, 16 Aug 2012, Michał Górny wrote:
>> > +dointo() {
>> > + [[ ${#} -gt 2 ]] || die 'Synopsis: dointo <directory>
>> > <file> [...]' +
>> > + local directory=${1}
>> > + shift
>> > +
>> > + (
>> > + insinto "${directory}"
>>
>> Shouldn't there be checking for errors here, for the case that insinto
>> fails?
> Hmm, I don't even know if insinto should ever fail.
It can fail if the underlying "install -d" fails, e.g. if a regular
file is in the way of the directory to be created.
> And if it does, then the following doins should fail as well, I
> guess.
Normally I also don't add any error checks for insinto in ebuilds.
But for a general eclass function, chances are higher that something
goes wrong. For example, arguments may be specified in the wrong
order. So some extra error checking cannot harm (and is cheap).
Ulrich
