Can a modified PKGBUILD file persist through updates w/ AUR helper?
I'm using an AUR helper (Yay) on an Arch Linux system. I want to modify the PKGBUILD file for a particular package (ffmpeg-git) prior to compiling the package (I'm enabling hardware encoding/decoding).
I think I see how to do this with
yay --editmenu -S ffmpeg-git
and adding the necessary switches with an editor from "within" Yay. When upgrading the system, I could do more or less the same thing.
This seems rather clunky, however. Arch Linux "wants" to be updated frequently and I'd prefer to reduce the touch-time associated with each update.
arch-linux package-management
add a comment |
I'm using an AUR helper (Yay) on an Arch Linux system. I want to modify the PKGBUILD file for a particular package (ffmpeg-git) prior to compiling the package (I'm enabling hardware encoding/decoding).
I think I see how to do this with
yay --editmenu -S ffmpeg-git
and adding the necessary switches with an editor from "within" Yay. When upgrading the system, I could do more or less the same thing.
This seems rather clunky, however. Arch Linux "wants" to be updated frequently and I'd prefer to reduce the touch-time associated with each update.
arch-linux package-management
add a comment |
I'm using an AUR helper (Yay) on an Arch Linux system. I want to modify the PKGBUILD file for a particular package (ffmpeg-git) prior to compiling the package (I'm enabling hardware encoding/decoding).
I think I see how to do this with
yay --editmenu -S ffmpeg-git
and adding the necessary switches with an editor from "within" Yay. When upgrading the system, I could do more or less the same thing.
This seems rather clunky, however. Arch Linux "wants" to be updated frequently and I'd prefer to reduce the touch-time associated with each update.
arch-linux package-management
I'm using an AUR helper (Yay) on an Arch Linux system. I want to modify the PKGBUILD file for a particular package (ffmpeg-git) prior to compiling the package (I'm enabling hardware encoding/decoding).
I think I see how to do this with
yay --editmenu -S ffmpeg-git
and adding the necessary switches with an editor from "within" Yay. When upgrading the system, I could do more or less the same thing.
This seems rather clunky, however. Arch Linux "wants" to be updated frequently and I'd prefer to reduce the touch-time associated with each update.
arch-linux package-management
arch-linux package-management
asked Dec 27 '18 at 8:12
eponymouseponymous
284
284
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The problem with persistent modifications to a PKGBUILD when using an AUR helper is that depending on which helper you use, you may not have the modified PKGBUILD cached at all, or it may require overwriting your local modifications in order to correctly pull updates for a -git package.
In the general case, this is sort of solved by customizepkg (and various clones or reinventions that run arbitrary commands or patches instead of configuration keys), but many AUR helpers do not implement this. Many experienced users will instead opt to git commit
their own changes to the PKGBUILD, and treat it as a personally-maintained package which they build by hand, periodically using git pull --rebase
to retrieve changes to the PKGBUILD and then replay their own changes on top.
"yay" in particular is an AUR helper which (as its manpage describes) is geared towards batch interactions and minimizing the amount of time spent paying attention to your updates. So even if it implemented customizepkg
, it would not detect updates to metadata (such as added dependencies) since it will not reinterpret the PKGBUILD after it is modified. Internally, it uses the AUR's json interface to resolve all recursive package dependencies even before downloading any PKGBUILDs.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1388051%2fcan-a-modified-pkgbuild-file-persist-through-updates-w-aur-helper%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
The problem with persistent modifications to a PKGBUILD when using an AUR helper is that depending on which helper you use, you may not have the modified PKGBUILD cached at all, or it may require overwriting your local modifications in order to correctly pull updates for a -git package.
In the general case, this is sort of solved by customizepkg (and various clones or reinventions that run arbitrary commands or patches instead of configuration keys), but many AUR helpers do not implement this. Many experienced users will instead opt to git commit
their own changes to the PKGBUILD, and treat it as a personally-maintained package which they build by hand, periodically using git pull --rebase
to retrieve changes to the PKGBUILD and then replay their own changes on top.
"yay" in particular is an AUR helper which (as its manpage describes) is geared towards batch interactions and minimizing the amount of time spent paying attention to your updates. So even if it implemented customizepkg
, it would not detect updates to metadata (such as added dependencies) since it will not reinterpret the PKGBUILD after it is modified. Internally, it uses the AUR's json interface to resolve all recursive package dependencies even before downloading any PKGBUILDs.
add a comment |
The problem with persistent modifications to a PKGBUILD when using an AUR helper is that depending on which helper you use, you may not have the modified PKGBUILD cached at all, or it may require overwriting your local modifications in order to correctly pull updates for a -git package.
In the general case, this is sort of solved by customizepkg (and various clones or reinventions that run arbitrary commands or patches instead of configuration keys), but many AUR helpers do not implement this. Many experienced users will instead opt to git commit
their own changes to the PKGBUILD, and treat it as a personally-maintained package which they build by hand, periodically using git pull --rebase
to retrieve changes to the PKGBUILD and then replay their own changes on top.
"yay" in particular is an AUR helper which (as its manpage describes) is geared towards batch interactions and minimizing the amount of time spent paying attention to your updates. So even if it implemented customizepkg
, it would not detect updates to metadata (such as added dependencies) since it will not reinterpret the PKGBUILD after it is modified. Internally, it uses the AUR's json interface to resolve all recursive package dependencies even before downloading any PKGBUILDs.
add a comment |
The problem with persistent modifications to a PKGBUILD when using an AUR helper is that depending on which helper you use, you may not have the modified PKGBUILD cached at all, or it may require overwriting your local modifications in order to correctly pull updates for a -git package.
In the general case, this is sort of solved by customizepkg (and various clones or reinventions that run arbitrary commands or patches instead of configuration keys), but many AUR helpers do not implement this. Many experienced users will instead opt to git commit
their own changes to the PKGBUILD, and treat it as a personally-maintained package which they build by hand, periodically using git pull --rebase
to retrieve changes to the PKGBUILD and then replay their own changes on top.
"yay" in particular is an AUR helper which (as its manpage describes) is geared towards batch interactions and minimizing the amount of time spent paying attention to your updates. So even if it implemented customizepkg
, it would not detect updates to metadata (such as added dependencies) since it will not reinterpret the PKGBUILD after it is modified. Internally, it uses the AUR's json interface to resolve all recursive package dependencies even before downloading any PKGBUILDs.
The problem with persistent modifications to a PKGBUILD when using an AUR helper is that depending on which helper you use, you may not have the modified PKGBUILD cached at all, or it may require overwriting your local modifications in order to correctly pull updates for a -git package.
In the general case, this is sort of solved by customizepkg (and various clones or reinventions that run arbitrary commands or patches instead of configuration keys), but many AUR helpers do not implement this. Many experienced users will instead opt to git commit
their own changes to the PKGBUILD, and treat it as a personally-maintained package which they build by hand, periodically using git pull --rebase
to retrieve changes to the PKGBUILD and then replay their own changes on top.
"yay" in particular is an AUR helper which (as its manpage describes) is geared towards batch interactions and minimizing the amount of time spent paying attention to your updates. So even if it implemented customizepkg
, it would not detect updates to metadata (such as added dependencies) since it will not reinterpret the PKGBUILD after it is modified. Internally, it uses the AUR's json interface to resolve all recursive package dependencies even before downloading any PKGBUILDs.
answered Dec 30 '18 at 1:50
eschwartzeschwartz
1065
1065
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1388051%2fcan-a-modified-pkgbuild-file-persist-through-updates-w-aur-helper%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