You are not logged in.
I am having trouble getting mksrcinfo find my PKGBUILD when the PKGBUILD is in a different directory ...
[dshub@cochlea tmp]$ pwd
/tmp
[dshub@cochlea tmp]$ ls -al dshub/
total 4
drwx------ 2 dshub dshub 60 Aug 29 13:01 .
drwxrwxrwt 25 root root 660 Aug 29 13:01 ..
-rw------- 1 dshub dshub 940 Aug 29 12:52 PKGBUILD
[dshub@cochlea tmp]$ mksrcinfo /tmp/dshub/PKGBUILD
==> ERROR: PKGBUILD not found in current directory
[dshub@cochlea tmp]$ mksrcinfo /tmp/dshub/
==> ERROR: PKGBUILD not found in current directory
[dshub@cochlea tmp]$ cd dshub
[dshub@cochlea dshub]$ mksrcinfo /tmp/dshub/
/usr/bin/mksrcinfo: line 196: .: /tmp/dshub/: is a directory
[dshub@cochlea dshub]$ mksrcinfo /tmp/dshub/PKGBUILD
Last edited by daniel_shub (2016-08-29 18:07:20)
Offline
mksrcinfo isn't useful really anymore. Use makepkg --printsrcinfo.
Online
That solves my issue (sort of). You need to run makepkg in the directory with the PKGBUILD (or alternative build file) and it cannot be run as root. Those issues are easy to work around and are documented.
Offline
mksrcinfo isn't useful really anymore. Use makepkg --printsrcinfo.
It is just as useful as it ever was. It is just that you can now do the same thing directly using makepkg.
Personally, I prefer `mksrcinfo` over `makepkg --printsrcinfo > .SRCINFO` because it is easier to type -- so +1 for mksrcinfo even as an alias.
...
@daniel_shub,
At one point, mksrcinfo accepted PKGBUILDs anywhere, but now that it uses makepkg behind the scenes, it is limited in the same way makepkg is.
Last edited by eschwartz (2016-08-29 23:22:13)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline