Calling makepkg from an outer directory
up vote
0
down vote
favorite
I realized that when I try to call makepkg command on a PKGBUILD in an inner file, for instance makepkg package_name/PKGBUILD, I get an error saying
==> ERROR: PKGBUILD does not exist.
But when I change my current directory to the directory of PKGBUILD file, cd package_name, and run makepkg PKGBUILD I face no problems. So, is it true that I have to strictly be in the PKGBUILD file's directory to be able to call makepkgon it?
Thanks
linux archlinux package-managers
asked Nov 13 at 13:12
Huzo
451214
add a comment |
up vote
0
down vote
favorite
I realized that when I try to call makepkg command on a PKGBUILD in an inner file, for instance makepkg package_name/PKGBUILD, I get an error saying
==> ERROR: PKGBUILD does not exist.
But when I change my current directory to the directory of PKGBUILD file, cd package_name, and run makepkg PKGBUILD I face no problems. So, is it true that I have to strictly be in the PKGBUILD file's directory to be able to call makepkgon it?
Thanks
linux archlinux package-managers
asked Nov 13 at 13:12
Huzo
451214
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I realized that when I try to call makepkg command on a PKGBUILD in an inner file, for instance makepkg package_name/PKGBUILD, I get an error saying
==> ERROR: PKGBUILD does not exist.
But when I change my current directory to the directory of PKGBUILD file, cd package_name, and run makepkg PKGBUILD I face no problems. So, is it true that I have to strictly be in the PKGBUILD file's directory to be able to call makepkgon it?
Thanks
linux archlinux package-managers
asked Nov 13 at 13:12
Huzo
451214
I realized that when I try to call makepkg command on a PKGBUILD in an inner file, for instance makepkg package_name/PKGBUILD, I get an error saying
==> ERROR: PKGBUILD does not exist.
But when I change my current directory to the directory of PKGBUILD file, cd package_name, and run makepkg PKGBUILD I face no problems. So, is it true that I have to strictly be in the PKGBUILD file's directory to be able to call makepkgon it?
Thanks
linux archlinux package-managers
linux archlinux package-managers
asked Nov 13 at 13:12
Huzo
451214
asked Nov 13 at 13:12
Huzo
451214
asked Nov 13 at 13:12
Huzo
451214
asked Nov 13 at 13:12
Huzo
451214
asked Nov 13 at 13:12
Huzo
451214
451214
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
Seems that way. If you are scripting this and want to avoid switching folders back and forth, an option can be to utilize a sub-shell like this
(cd package_name && makepkg PKGBUILD)
which will then transport you back to current folder after finishing the actions within the parentheses.
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
add a comment |
up vote
1
down vote
The command makepkg PKGBUILD does not do what you think it does. makepkg does not accept the name of a PKGBUILD as a positional parameter, and it completely discards this entirely.
As per the manpage, if you wish to specify a PKGBUILD to use, you must use the -p <buildscript> option. Also as per the manpage, "The buildscript must be located in the directory makepkg is called from."
$ makepkg -p package_name/PKGBUILD
==> ERROR: package_name/PKGBUILD must be in the current working directory.
As you can see, makepkg contains code to ensure you don't try doing something which it does not allow you to do -- but you must correctly use the makepkg command-line options in order for makepkg to recognize what you're trying to do and tell you what you did wrong.
answered Nov 23 at 18:36
eschwartz
9611
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Seems that way. If you are scripting this and want to avoid switching folders back and forth, an option can be to utilize a sub-shell like this
(cd package_name && makepkg PKGBUILD)
which will then transport you back to current folder after finishing the actions within the parentheses.
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
add a comment |
up vote
1
down vote
accepted
Seems that way. If you are scripting this and want to avoid switching folders back and forth, an option can be to utilize a sub-shell like this
(cd package_name && makepkg PKGBUILD)
which will then transport you back to current folder after finishing the actions within the parentheses.
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Seems that way. If you are scripting this and want to avoid switching folders back and forth, an option can be to utilize a sub-shell like this
(cd package_name && makepkg PKGBUILD)
which will then transport you back to current folder after finishing the actions within the parentheses.
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
Seems that way. If you are scripting this and want to avoid switching folders back and forth, an option can be to utilize a sub-shell like this
(cd package_name && makepkg PKGBUILD)
which will then transport you back to current folder after finishing the actions within the parentheses.
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
edited Nov 17 at 1:24
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
answered Nov 16 at 18:41
Harald Nordgren
5,20121338
5,20121338
add a comment |
add a comment |
up vote
1
down vote
The command makepkg PKGBUILD does not do what you think it does. makepkg does not accept the name of a PKGBUILD as a positional parameter, and it completely discards this entirely.
As per the manpage, if you wish to specify a PKGBUILD to use, you must use the -p <buildscript> option. Also as per the manpage, "The buildscript must be located in the directory makepkg is called from."
$ makepkg -p package_name/PKGBUILD
==> ERROR: package_name/PKGBUILD must be in the current working directory.
As you can see, makepkg contains code to ensure you don't try doing something which it does not allow you to do -- but you must correctly use the makepkg command-line options in order for makepkg to recognize what you're trying to do and tell you what you did wrong.
answered Nov 23 at 18:36
eschwartz
9611
add a comment |
up vote
1
down vote
The command makepkg PKGBUILD does not do what you think it does. makepkg does not accept the name of a PKGBUILD as a positional parameter, and it completely discards this entirely.
As per the manpage, if you wish to specify a PKGBUILD to use, you must use the -p <buildscript> option. Also as per the manpage, "The buildscript must be located in the directory makepkg is called from."
$ makepkg -p package_name/PKGBUILD
==> ERROR: package_name/PKGBUILD must be in the current working directory.
As you can see, makepkg contains code to ensure you don't try doing something which it does not allow you to do -- but you must correctly use the makepkg command-line options in order for makepkg to recognize what you're trying to do and tell you what you did wrong.
answered Nov 23 at 18:36
eschwartz
9611
add a comment |
up vote
1
down vote
up vote
1
down vote
The command makepkg PKGBUILD does not do what you think it does. makepkg does not accept the name of a PKGBUILD as a positional parameter, and it completely discards this entirely.
As per the manpage, if you wish to specify a PKGBUILD to use, you must use the -p <buildscript> option. Also as per the manpage, "The buildscript must be located in the directory makepkg is called from."
$ makepkg -p package_name/PKGBUILD
==> ERROR: package_name/PKGBUILD must be in the current working directory.
As you can see, makepkg contains code to ensure you don't try doing something which it does not allow you to do -- but you must correctly use the makepkg command-line options in order for makepkg to recognize what you're trying to do and tell you what you did wrong.
answered Nov 23 at 18:36
eschwartz
9611
The command makepkg PKGBUILD does not do what you think it does. makepkg does not accept the name of a PKGBUILD as a positional parameter, and it completely discards this entirely.
As per the manpage, if you wish to specify a PKGBUILD to use, you must use the -p <buildscript> option. Also as per the manpage, "The buildscript must be located in the directory makepkg is called from."
$ makepkg -p package_name/PKGBUILD
==> ERROR: package_name/PKGBUILD must be in the current working directory.
As you can see, makepkg contains code to ensure you don't try doing something which it does not allow you to do -- but you must correctly use the makepkg command-line options in order for makepkg to recognize what you're trying to do and tell you what you did wrong.
answered Nov 23 at 18:36
eschwartz
9611
answered Nov 23 at 18:36
eschwartz
9611
answered Nov 23 at 18:36
eschwartz
9611
answered Nov 23 at 18:36
eschwartz
9611
9611
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53281773%2fcalling-makepkg-from-an-outer-directory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
