Mr Green just tested a package I've built, and got this error:
==> Found jd4xarch.patch in build dir
==> Found jd4x.sh in build dir
==> Validating source files with MD5sums
jd4x-src-v0.2b13.tar.gz ... Passed
looks-1_2_1.zip ... Passed
jd4xarch.patch ... Passed
jd4x.sh ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf jd4x-src-v0.2b13.tar.gz
==> unzip -qqo looks-1_2_1.zip
/usr/bin/makepkg: line 473: unzip: command not found
==> ERROR: Failed to extract looks-1_2_1.zip
pacman -Sy unzip and then rerunning makepkg fixed the problem. My question is if unzip should be a make dependency for the package I've built.
I actually think that makepkg should depend on unzip, if it uses unzip to access files stored in the zip format. It automatically unzips (or untars) packages, so it needs unzip to operate, no?
Is this a feature or a bug; should I report it?
I think you should just make "unzip" a makedepend.
"Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
We, the developers, have just talked about this. Because makepkg uses unzip to uncompress the file and it's not strictly part of the build system, it doesn't need to be part of the PKGBUILD.
There are assumptions that can be made with PKGBUILDs, and having unzip to unzip source files is one of them.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal