On Tuesday 21 April 2009 18:39:38 Greg KH wrote:
> Ok, I know I'm doing something stupid here, but I can't figure it out.
>
> I have a new ebuild (linux-firmware) that is really just a tarball that
> needs to be placed somewhere in the filesystem.
>
> So, I do the following:
> src_install() {
> dodir /lib/firmware
> cp -R "${S}/*" "${D}lib/firmware/" || die "Install failed!"
> }
>
What I would do is the following
src_install() {
insinto /lib/firmware/
doins -r "${S}"/* || die "doins failed"
}
> but that fails badly:
> >>> Install linux-firmware-20090421 into
> >>> /var/tmp/portage/sys-kernel/linux-firmware-20090421/image/ category
> >>> sys-kernel
>
> cp: cannot stat
> `/var/tmp/portage/sys-kernel/linux-firmware-20090421/work/linux-firmware-20
>090421/*': No such file or directory
>
> Yet the files are really in that directory.
>
> I can't drop the trailing "*" on the cp command, otherwise we get the
> directory name that the firmware was expanded into during unpack into
> lib/firmware/.
>
> So, anyone want to apply the cluestick?
>
> thanks,
>
> greg k-h-- Markos Chandras (hwoarang) Gentoo Linux Developer Qt/KDE/Sunrise/Sound Web: http://hwoarang.silverarrow.gr
signature.asc
Description: This is a digitally signed message part.
