1 |
Ok, I know I'm doing something stupid here, but I can't figure it out. |
2 |
|
3 |
I have a new ebuild (linux-firmware) that is really just a tarball that |
4 |
needs to be placed somewhere in the filesystem. |
5 |
|
6 |
So, I do the following: |
7 |
src_install() { |
8 |
dodir /lib/firmware |
9 |
cp -R "${S}/*" "${D}lib/firmware/" || die "Install failed!" |
10 |
} |
11 |
|
12 |
but that fails badly: |
13 |
>>> Install linux-firmware-20090421 into /var/tmp/portage/sys-kernel/linux-firmware-20090421/image/ category sys-kernel |
14 |
cp: cannot stat `/var/tmp/portage/sys-kernel/linux-firmware-20090421/work/linux-firmware-20090421/*': No such file or directory |
15 |
|
16 |
Yet the files are really in that directory. |
17 |
|
18 |
I can't drop the trailing "*" on the cp command, otherwise we get the |
19 |
directory name that the firmware was expanded into during unpack into |
20 |
lib/firmware/. |
21 |
|
22 |
So, anyone want to apply the cluestick? |
23 |
|
24 |
thanks, |
25 |
|
26 |
greg k-h |