Multiple prefix tags in rpm spec file
I have an rpm that builds two packages. I tried to add separate Prefix tags in the preamble each of the packages.
However, as there is one prep section, I am not able to address the prefix each of the packages individually. (%prefix indicates only the Prefix of the subpackage)
Is there a way to specify package-specific prefix?
rpm rpmbuild
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have an rpm that builds two packages. I tried to add separate Prefix tags in the preamble each of the packages.
However, as there is one prep section, I am not able to address the prefix each of the packages individually. (%prefix indicates only the Prefix of the subpackage)
Is there a way to specify package-specific prefix?
rpm rpmbuild
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
%packagename-prefix
?
– wurtel
Dec 17 '14 at 12:52
that didn't work for me!
– navster
Dec 18 '14 at 10:24
add a comment |
I have an rpm that builds two packages. I tried to add separate Prefix tags in the preamble each of the packages.
However, as there is one prep section, I am not able to address the prefix each of the packages individually. (%prefix indicates only the Prefix of the subpackage)
Is there a way to specify package-specific prefix?
rpm rpmbuild
I have an rpm that builds two packages. I tried to add separate Prefix tags in the preamble each of the packages.
However, as there is one prep section, I am not able to address the prefix each of the packages individually. (%prefix indicates only the Prefix of the subpackage)
Is there a way to specify package-specific prefix?
rpm rpmbuild
rpm rpmbuild
asked Dec 17 '14 at 10:03
navsternavster
162
162
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
%packagename-prefix
?
– wurtel
Dec 17 '14 at 12:52
that didn't work for me!
– navster
Dec 18 '14 at 10:24
add a comment |
%packagename-prefix
?
– wurtel
Dec 17 '14 at 12:52
that didn't work for me!
– navster
Dec 18 '14 at 10:24
%packagename-prefix
?– wurtel
Dec 17 '14 at 12:52
%packagename-prefix
?– wurtel
Dec 17 '14 at 12:52
that didn't work for me!
– navster
Dec 18 '14 at 10:24
that didn't work for me!
– navster
Dec 18 '14 at 10:24
add a comment |
1 Answer
1
active
oldest
votes
Use macros like {%prefix1} to name multiple prefixes and then use syntax like "Prefix: %{prefix1}". I'm not sure what you are expecting from multiple prefixes in rpm packaging. Prefixes were designed for relocatable packages, but all paths in a *.rpm package can be relocated during install. Adding an explicit Prefix: just disables a warning message.
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%2f174635%2fmultiple-prefix-tags-in-rpm-spec-file%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
Use macros like {%prefix1} to name multiple prefixes and then use syntax like "Prefix: %{prefix1}". I'm not sure what you are expecting from multiple prefixes in rpm packaging. Prefixes were designed for relocatable packages, but all paths in a *.rpm package can be relocated during install. Adding an explicit Prefix: just disables a warning message.
add a comment |
Use macros like {%prefix1} to name multiple prefixes and then use syntax like "Prefix: %{prefix1}". I'm not sure what you are expecting from multiple prefixes in rpm packaging. Prefixes were designed for relocatable packages, but all paths in a *.rpm package can be relocated during install. Adding an explicit Prefix: just disables a warning message.
add a comment |
Use macros like {%prefix1} to name multiple prefixes and then use syntax like "Prefix: %{prefix1}". I'm not sure what you are expecting from multiple prefixes in rpm packaging. Prefixes were designed for relocatable packages, but all paths in a *.rpm package can be relocated during install. Adding an explicit Prefix: just disables a warning message.
Use macros like {%prefix1} to name multiple prefixes and then use syntax like "Prefix: %{prefix1}". I'm not sure what you are expecting from multiple prefixes in rpm packaging. Prefixes were designed for relocatable packages, but all paths in a *.rpm package can be relocated during install. Adding an explicit Prefix: just disables a warning message.
answered Jan 5 '15 at 15:54
Jeff JohnsonJeff Johnson
40624
40624
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%2f174635%2fmultiple-prefix-tags-in-rpm-spec-file%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
%packagename-prefix
?– wurtel
Dec 17 '14 at 12:52
that didn't work for me!
– navster
Dec 18 '14 at 10:24