How to create a .deb package using the source code which would compile and install automatically when .deb is...
I have the source code and need to crate a .deb package. When it is installed.., it shld compile the source code and install the resulting binaries when the deb package is installed.
I know creating the package when we already have the binaries.
I just have a abstract idea. Has it something to do with creating a PRE_INSTALL script which would compile the source code to give the binaries.., which later would be installed ?
linux scripting package-management debian-installer packaging
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
add a comment |
I have the source code and need to crate a .deb package. When it is installed.., it shld compile the source code and install the resulting binaries when the deb package is installed.
I know creating the package when we already have the binaries.
I just have a abstract idea. Has it something to do with creating a PRE_INSTALL script which would compile the source code to give the binaries.., which later would be installed ?
linux scripting package-management debian-installer packaging
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
add a comment |
I have the source code and need to crate a .deb package. When it is installed.., it shld compile the source code and install the resulting binaries when the deb package is installed.
I know creating the package when we already have the binaries.
I just have a abstract idea. Has it something to do with creating a PRE_INSTALL script which would compile the source code to give the binaries.., which later would be installed ?
linux scripting package-management debian-installer packaging
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
I have the source code and need to crate a .deb package. When it is installed.., it shld compile the source code and install the resulting binaries when the deb package is installed.
I know creating the package when we already have the binaries.
I just have a abstract idea. Has it something to do with creating a PRE_INSTALL script which would compile the source code to give the binaries.., which later would be installed ?
linux scripting package-management debian-installer packaging
linux scripting package-management debian-installer packaging
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
edited Jan 10 at 19:02
Rui F Ribeiro
39.5k1479133
39.5k1479133
asked Jan 9 at 15:56
manojh93manojh93
61
asked Jan 9 at 15:56
manojh93manojh93
61
asked Jan 9 at 15:56
manojh93manojh93
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It is possible to do this by specifying your package as "all" architectures and using post-install and pre-remove scripts (not pre-install). But this is a very bad idea. It undermines a lot of what .deb files are intended to be.
You will need to make your .deb file dependent on the compiler (gcc?) as well as the development package for any libraries your code depends on, not just the library themselves.
You will need to create a post-install script to compile the code, and put the binaries in the right places. You will need to create a pre-remove script to delete all the installed binaries when the package is deleted.
Even after that, you will be left with a package that doesn't correctly inform the dpkg installer where all the binaries are. It will not be able to detect collisions between your package and others.
This is a really bad idea, I strongly suggest you don't do it.
answered Jan 9 at 16:37
coulingcouling
401311
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%2f493488%2fhow-to-create-a-deb-package-using-the-source-code-which-would-compile-and-insta%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is possible to do this by specifying your package as "all" architectures and using post-install and pre-remove scripts (not pre-install). But this is a very bad idea. It undermines a lot of what .deb files are intended to be.
You will need to make your .deb file dependent on the compiler (gcc?) as well as the development package for any libraries your code depends on, not just the library themselves.
You will need to create a post-install script to compile the code, and put the binaries in the right places. You will need to create a pre-remove script to delete all the installed binaries when the package is deleted.
Even after that, you will be left with a package that doesn't correctly inform the dpkg installer where all the binaries are. It will not be able to detect collisions between your package and others.
This is a really bad idea, I strongly suggest you don't do it.
answered Jan 9 at 16:37
coulingcouling
401311
add a comment |
It is possible to do this by specifying your package as "all" architectures and using post-install and pre-remove scripts (not pre-install). But this is a very bad idea. It undermines a lot of what .deb files are intended to be.
You will need to make your .deb file dependent on the compiler (gcc?) as well as the development package for any libraries your code depends on, not just the library themselves.
You will need to create a post-install script to compile the code, and put the binaries in the right places. You will need to create a pre-remove script to delete all the installed binaries when the package is deleted.
Even after that, you will be left with a package that doesn't correctly inform the dpkg installer where all the binaries are. It will not be able to detect collisions between your package and others.
This is a really bad idea, I strongly suggest you don't do it.
answered Jan 9 at 16:37
coulingcouling
401311
add a comment |
It is possible to do this by specifying your package as "all" architectures and using post-install and pre-remove scripts (not pre-install). But this is a very bad idea. It undermines a lot of what .deb files are intended to be.
You will need to make your .deb file dependent on the compiler (gcc?) as well as the development package for any libraries your code depends on, not just the library themselves.
You will need to create a post-install script to compile the code, and put the binaries in the right places. You will need to create a pre-remove script to delete all the installed binaries when the package is deleted.
Even after that, you will be left with a package that doesn't correctly inform the dpkg installer where all the binaries are. It will not be able to detect collisions between your package and others.
This is a really bad idea, I strongly suggest you don't do it.
answered Jan 9 at 16:37
coulingcouling
401311
It is possible to do this by specifying your package as "all" architectures and using post-install and pre-remove scripts (not pre-install). But this is a very bad idea. It undermines a lot of what .deb files are intended to be.
You will need to make your .deb file dependent on the compiler (gcc?) as well as the development package for any libraries your code depends on, not just the library themselves.
You will need to create a post-install script to compile the code, and put the binaries in the right places. You will need to create a pre-remove script to delete all the installed binaries when the package is deleted.
Even after that, you will be left with a package that doesn't correctly inform the dpkg installer where all the binaries are. It will not be able to detect collisions between your package and others.
This is a really bad idea, I strongly suggest you don't do it.
answered Jan 9 at 16:37
coulingcouling
401311
answered Jan 9 at 16:37
coulingcouling
401311
answered Jan 9 at 16:37
coulingcouling
401311
answered Jan 9 at 16:37
coulingcouling
401311
401311
add a comment |
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%2f493488%2fhow-to-create-a-deb-package-using-the-source-code-which-would-compile-and-insta%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
