How to pass parameters for Debian installer (.deb)
up vote
2
down vote
favorite
I am developing a specialized Unix application that has the Debian installer (.deb). It needs to get few simple string values during installation. These values must be picked by the post-install bash script.
What would be most reasonable, approved way top pass these values to the post install script?
software-installation debian-installer
add a comment |
up vote
2
down vote
favorite
I am developing a specialized Unix application that has the Debian installer (.deb). It needs to get few simple string values during installation. These values must be picked by the post-install bash script.
What would be most reasonable, approved way top pass these values to the post install script?
software-installation debian-installer
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am developing a specialized Unix application that has the Debian installer (.deb). It needs to get few simple string values during installation. These values must be picked by the post-install bash script.
What would be most reasonable, approved way top pass these values to the post install script?
software-installation debian-installer
I am developing a specialized Unix application that has the Debian installer (.deb). It needs to get few simple string values during installation. These values must be picked by the post-install bash script.
What would be most reasonable, approved way top pass these values to the post install script?
software-installation debian-installer
software-installation debian-installer
asked 2 hours ago
h22
361110
361110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
The “approved” way to do this is to use debconf
. This might seem surprising if you’re not interested in actually prompting the user for the information; but beyond prompting, debconf
is based on the notion of package configuration variables, and prompting is only one of the ways that can be used to provide the values for those variables. The debconf-devel
manpage describes how to use this.
In your case, you’d declare the variables in your package’s templates and config
script, and then use them in your postinst
. To feed the values in without prompting, you’d then use pre-seeding:
write a file containing the keys and values:
<package> <config key> <config type> <value>
...
before installing the package, store its configuration:
debconf-set-selections < preseed-file
See Automating the installation of individual debian 8 packages with interactive prompts for an example.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The “approved” way to do this is to use debconf
. This might seem surprising if you’re not interested in actually prompting the user for the information; but beyond prompting, debconf
is based on the notion of package configuration variables, and prompting is only one of the ways that can be used to provide the values for those variables. The debconf-devel
manpage describes how to use this.
In your case, you’d declare the variables in your package’s templates and config
script, and then use them in your postinst
. To feed the values in without prompting, you’d then use pre-seeding:
write a file containing the keys and values:
<package> <config key> <config type> <value>
...
before installing the package, store its configuration:
debconf-set-selections < preseed-file
See Automating the installation of individual debian 8 packages with interactive prompts for an example.
add a comment |
up vote
2
down vote
The “approved” way to do this is to use debconf
. This might seem surprising if you’re not interested in actually prompting the user for the information; but beyond prompting, debconf
is based on the notion of package configuration variables, and prompting is only one of the ways that can be used to provide the values for those variables. The debconf-devel
manpage describes how to use this.
In your case, you’d declare the variables in your package’s templates and config
script, and then use them in your postinst
. To feed the values in without prompting, you’d then use pre-seeding:
write a file containing the keys and values:
<package> <config key> <config type> <value>
...
before installing the package, store its configuration:
debconf-set-selections < preseed-file
See Automating the installation of individual debian 8 packages with interactive prompts for an example.
add a comment |
up vote
2
down vote
up vote
2
down vote
The “approved” way to do this is to use debconf
. This might seem surprising if you’re not interested in actually prompting the user for the information; but beyond prompting, debconf
is based on the notion of package configuration variables, and prompting is only one of the ways that can be used to provide the values for those variables. The debconf-devel
manpage describes how to use this.
In your case, you’d declare the variables in your package’s templates and config
script, and then use them in your postinst
. To feed the values in without prompting, you’d then use pre-seeding:
write a file containing the keys and values:
<package> <config key> <config type> <value>
...
before installing the package, store its configuration:
debconf-set-selections < preseed-file
See Automating the installation of individual debian 8 packages with interactive prompts for an example.
The “approved” way to do this is to use debconf
. This might seem surprising if you’re not interested in actually prompting the user for the information; but beyond prompting, debconf
is based on the notion of package configuration variables, and prompting is only one of the ways that can be used to provide the values for those variables. The debconf-devel
manpage describes how to use this.
In your case, you’d declare the variables in your package’s templates and config
script, and then use them in your postinst
. To feed the values in without prompting, you’d then use pre-seeding:
write a file containing the keys and values:
<package> <config key> <config type> <value>
...
before installing the package, store its configuration:
debconf-set-selections < preseed-file
See Automating the installation of individual debian 8 packages with interactive prompts for an example.
answered 2 hours ago
Stephen Kitt
156k23343416
156k23343416
add a comment |
add a comment |
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%2f482092%2fhow-to-pass-parameters-for-debian-installer-deb%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