How can I avoid the prompts when installing a FreeBSD port?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
When I install a port, I am often presented with a menu screen to select configuration options. If I'm going to install a really big package with lots of dependencies, that will be extremely inconvenient. Is there a make flag for accepting the default answers for all such prompts?
freebsd bsd-ports
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
add a comment |
When I install a port, I am often presented with a menu screen to select configuration options. If I'm going to install a really big package with lots of dependencies, that will be extremely inconvenient. Is there a make flag for accepting the default answers for all such prompts?
freebsd bsd-ports
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
add a comment |
When I install a port, I am often presented with a menu screen to select configuration options. If I'm going to install a really big package with lots of dependencies, that will be extremely inconvenient. Is there a make flag for accepting the default answers for all such prompts?
freebsd bsd-ports
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
When I install a port, I am often presented with a menu screen to select configuration options. If I'm going to install a really big package with lots of dependencies, that will be extremely inconvenient. Is there a make flag for accepting the default answers for all such prompts?
freebsd bsd-ports
freebsd bsd-ports
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
asked Dec 30 '10 at 19:20
JCCyCJCCyC
4061718
4061718
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Probably BATCH, described in ports(7), is what you're looking for:
# cd /usr/ports/sysutils/screen
# export BATCH=yes
# make rmconfig
# make install clean
(no configuration menu is displayed)
make rmconfig removes OPTIONS config for this port, and you can use it to remove OPTIONS which were previously saved when you configured and installed screen(1) the first time. OPTIONS are stored to directory which is specifed via PORT_DB_DIR (defaults to /var/db/ports).
If you use bash, BATCH can be set automatically every time you log in:
# echo 'export BATCH=yes' >> ~/.bash_profile
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
12
I prefermake config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.
– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
Also please runmake config-recursivemultiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.
– Alex Hirzel
Mar 6 '13 at 15:22
exportwill only work onshwhich is not the FreeBSD default shell
– ajeh
Aug 2 '17 at 18:10
add a comment |
I think it's worth mentioning that you might not always want to do this. I seem to remember, for instance, needing to config emacs to add xft support. If you want to bypass the prompts for a single build,
make install clean BATCH=yes
will work as well.
answered Jan 29 '11 at 23:58
hydohydo
30114
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting thatmake install clean BATCH=has the same effect, as according to the manual forports(7), it must only be defined. It can be set to anything or nothing at all
– Harold Fischer
Jun 26 '18 at 15:28
add a comment |
This doesn't automatically accept defaults like you're asking, but I like the "make config-recursive" method which runs you through any options for the port you want as well as options for all dependencies. You don't have to change anything if you don't want to, but you go through all selection screens at once rather than whenever the building process arrives at them.
Once that's done, your "make install clean" should go pretty much unattended.
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run ofmake config-recursive.
– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2funix.stackexchange.com%2fquestions%2f5257%2fhow-can-i-avoid-the-prompts-when-installing-a-freebsd-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Probably BATCH, described in ports(7), is what you're looking for:
# cd /usr/ports/sysutils/screen
# export BATCH=yes
# make rmconfig
# make install clean
(no configuration menu is displayed)
make rmconfig removes OPTIONS config for this port, and you can use it to remove OPTIONS which were previously saved when you configured and installed screen(1) the first time. OPTIONS are stored to directory which is specifed via PORT_DB_DIR (defaults to /var/db/ports).
If you use bash, BATCH can be set automatically every time you log in:
# echo 'export BATCH=yes' >> ~/.bash_profile
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
12
I prefermake config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.
– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
Also please runmake config-recursivemultiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.
– Alex Hirzel
Mar 6 '13 at 15:22
exportwill only work onshwhich is not the FreeBSD default shell
– ajeh
Aug 2 '17 at 18:10
add a comment |
Probably BATCH, described in ports(7), is what you're looking for:
# cd /usr/ports/sysutils/screen
# export BATCH=yes
# make rmconfig
# make install clean
(no configuration menu is displayed)
make rmconfig removes OPTIONS config for this port, and you can use it to remove OPTIONS which were previously saved when you configured and installed screen(1) the first time. OPTIONS are stored to directory which is specifed via PORT_DB_DIR (defaults to /var/db/ports).
If you use bash, BATCH can be set automatically every time you log in:
# echo 'export BATCH=yes' >> ~/.bash_profile
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
12
I prefermake config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.
– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
Also please runmake config-recursivemultiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.
– Alex Hirzel
Mar 6 '13 at 15:22
exportwill only work onshwhich is not the FreeBSD default shell
– ajeh
Aug 2 '17 at 18:10
add a comment |
Probably BATCH, described in ports(7), is what you're looking for:
# cd /usr/ports/sysutils/screen
# export BATCH=yes
# make rmconfig
# make install clean
(no configuration menu is displayed)
make rmconfig removes OPTIONS config for this port, and you can use it to remove OPTIONS which were previously saved when you configured and installed screen(1) the first time. OPTIONS are stored to directory which is specifed via PORT_DB_DIR (defaults to /var/db/ports).
If you use bash, BATCH can be set automatically every time you log in:
# echo 'export BATCH=yes' >> ~/.bash_profile
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
Probably BATCH, described in ports(7), is what you're looking for:
# cd /usr/ports/sysutils/screen
# export BATCH=yes
# make rmconfig
# make install clean
(no configuration menu is displayed)
make rmconfig removes OPTIONS config for this port, and you can use it to remove OPTIONS which were previously saved when you configured and installed screen(1) the first time. OPTIONS are stored to directory which is specifed via PORT_DB_DIR (defaults to /var/db/ports).
If you use bash, BATCH can be set automatically every time you log in:
# echo 'export BATCH=yes' >> ~/.bash_profile
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
41.9k1483142
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
answered Jan 15 '11 at 9:53
Yasir ArsanukaevYasir Arsanukaev
35126
35126
12
I prefermake config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.
– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
Also please runmake config-recursivemultiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.
– Alex Hirzel
Mar 6 '13 at 15:22
exportwill only work onshwhich is not the FreeBSD default shell
– ajeh
Aug 2 '17 at 18:10
add a comment |
12
I prefermake config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.
– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
Also please runmake config-recursivemultiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.
– Alex Hirzel
Mar 6 '13 at 15:22
exportwill only work onshwhich is not the FreeBSD default shell
– ajeh
Aug 2 '17 at 18:10
12
12
I prefer
make config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.– user569825
Sep 16 '12 at 11:56
I prefer
make config-recursive && make install clean, as it gives you all config-dialogs upfront while the actual installation will likely work unattended.– user569825
Sep 16 '12 at 11:56
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
Also, to shorten your workload required for configuration, it's often a reasonable idea to exclusively look at the options that are active by default and just consider deactivating any of those.
– user569825
Sep 16 '12 at 12:01
7
7
Also please run
make config-recursive multiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.– Alex Hirzel
Mar 6 '13 at 15:22
Also please run
make config-recursive multiple times until you stop getting new options (i.e. at least twice). Any time you change an option, it may bring in another dependency that has yet more options.– Alex Hirzel
Mar 6 '13 at 15:22
export will only work on sh which is not the FreeBSD default shell– ajeh
Aug 2 '17 at 18:10
export will only work on sh which is not the FreeBSD default shell– ajeh
Aug 2 '17 at 18:10
add a comment |
I think it's worth mentioning that you might not always want to do this. I seem to remember, for instance, needing to config emacs to add xft support. If you want to bypass the prompts for a single build,
make install clean BATCH=yes
will work as well.
answered Jan 29 '11 at 23:58
hydohydo
30114
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting thatmake install clean BATCH=has the same effect, as according to the manual forports(7), it must only be defined. It can be set to anything or nothing at all
– Harold Fischer
Jun 26 '18 at 15:28
add a comment |
I think it's worth mentioning that you might not always want to do this. I seem to remember, for instance, needing to config emacs to add xft support. If you want to bypass the prompts for a single build,
make install clean BATCH=yes
will work as well.
answered Jan 29 '11 at 23:58
hydohydo
30114
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting thatmake install clean BATCH=has the same effect, as according to the manual forports(7), it must only be defined. It can be set to anything or nothing at all
– Harold Fischer
Jun 26 '18 at 15:28
add a comment |
I think it's worth mentioning that you might not always want to do this. I seem to remember, for instance, needing to config emacs to add xft support. If you want to bypass the prompts for a single build,
make install clean BATCH=yes
will work as well.
answered Jan 29 '11 at 23:58
hydohydo
30114
I think it's worth mentioning that you might not always want to do this. I seem to remember, for instance, needing to config emacs to add xft support. If you want to bypass the prompts for a single build,
make install clean BATCH=yes
will work as well.
answered Jan 29 '11 at 23:58
hydohydo
30114
answered Jan 29 '11 at 23:58
hydohydo
30114
answered Jan 29 '11 at 23:58
hydohydo
30114
answered Jan 29 '11 at 23:58
hydohydo
30114
30114
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting thatmake install clean BATCH=has the same effect, as according to the manual forports(7), it must only be defined. It can be set to anything or nothing at all
– Harold Fischer
Jun 26 '18 at 15:28
add a comment |
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting thatmake install clean BATCH=has the same effect, as according to the manual forports(7), it must only be defined. It can be set to anything or nothing at all
– Harold Fischer
Jun 26 '18 at 15:28
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
somehow works better than putting "BATCH=yes" in the front of make. Thanks.
– hari
Jan 18 '12 at 0:28
Worth noting that
make install clean BATCH= has the same effect, as according to the manual for ports(7), it must only be defined. It can be set to anything or nothing at all– Harold Fischer
Jun 26 '18 at 15:28
Worth noting that
make install clean BATCH= has the same effect, as according to the manual for ports(7), it must only be defined. It can be set to anything or nothing at all– Harold Fischer
Jun 26 '18 at 15:28
add a comment |
This doesn't automatically accept defaults like you're asking, but I like the "make config-recursive" method which runs you through any options for the port you want as well as options for all dependencies. You don't have to change anything if you don't want to, but you go through all selection screens at once rather than whenever the building process arrives at them.
Once that's done, your "make install clean" should go pretty much unattended.
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run ofmake config-recursive.
– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
add a comment |
This doesn't automatically accept defaults like you're asking, but I like the "make config-recursive" method which runs you through any options for the port you want as well as options for all dependencies. You don't have to change anything if you don't want to, but you go through all selection screens at once rather than whenever the building process arrives at them.
Once that's done, your "make install clean" should go pretty much unattended.
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run ofmake config-recursive.
– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
add a comment |
This doesn't automatically accept defaults like you're asking, but I like the "make config-recursive" method which runs you through any options for the port you want as well as options for all dependencies. You don't have to change anything if you don't want to, but you go through all selection screens at once rather than whenever the building process arrives at them.
Once that's done, your "make install clean" should go pretty much unattended.
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
This doesn't automatically accept defaults like you're asking, but I like the "make config-recursive" method which runs you through any options for the port you want as well as options for all dependencies. You don't have to change anything if you don't want to, but you go through all selection screens at once rather than whenever the building process arrives at them.
Once that's done, your "make install clean" should go pretty much unattended.
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
answered Apr 29 '11 at 22:42
FreeeBSD AdminFreeeBSD Admin
16112
16112
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run ofmake config-recursive.
– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
add a comment |
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run ofmake config-recursive.
– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
3
3
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run of
make config-recursive.– Alex Hirzel
Mar 6 '13 at 15:23
As I said on @Yasir's post--make sure to run this multiple times. If you change an option which brings in another dependency, if that dependency has options to configure you won't touch it until the next run of
make config-recursive.– Alex Hirzel
Mar 6 '13 at 15:23
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
Personally think this should be the accepted answer.
– revprez
Dec 24 '16 at 23:59
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f5257%2fhow-can-i-avoid-the-prompts-when-installing-a-freebsd-port%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
