Best Practices For Maintaining Pkgfile Customizations
I've been using this topic to spend time reviewing the CRUX mailing list archive and haven't seen it discussed. I would do the same with the IRC archives but am not ready to research how to filter all those TRs just now (is there a decent tool?). I gather folks just edit their local copies as needed. Do the pkgutils ever walk over those changes? Is it part of the CRUX philosophy that everyone should reinvent their own wheel when it comes to modifying touchy things like core packages? The lack of documentation about approaches to making installation changes suggests that conclusion. Are there any good approaches to maintaining one's localized package tweaks across prt-get sysup and release upgrades? -- <not cent from sell> May the LORD God bless you exceedingly abundantly! Dave_Craig______________________________________________ "So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe." __--from_Nightfall_by_Asimov/Silverberg_________________
Fellow CRUX users, On 17/06, David L. Craig wrote:
Are there any good approaches to maintaining one's localized package tweaks across prt-get sysup and release upgrades?
As a CRUX novice, I too would be interested in what people do in this situation. Most (if not all) configuration of some packages that I use (dwm, st, surf...) is done at compile time, in the config.h file. Unfortunately any modification is silently erased at every upgrade. I would probably fork the port, possibly include personal patches, customise the Pkgfile at will, and install the forked port instead. This, however, makes the upgrade process more cumbersome than it was since one does now not only have to `prt-get sysup` but also to pull the potential updates of the official ports into all of its personal ones and also upgrade them. I feel like a smart(er) package manager could have a construct to try applying custom patches to official ports (and require an intervention if that fails). On the one hand I realize the extra complexity layer that this would represent, but on the other it seems to me that forking every port that I want to patch is not the optimal solution. That's why I would really like to know in which way you deal with this problem yourselves. Best regards, Virgile Andreani
Hello, On Sat, Jul 25, 2015 at 8:13 PM, Virgile Andreani < virgile.andreani@anbuco.fr> wrote:
On 17/06, David L. Craig wrote:
Are there any good approaches to maintaining one's localized package tweaks across prt-get sysup and release upgrades?
As a CRUX novice, I too would be interested in what people do in this situation. Most (if not all) configuration of some packages that I use (dwm, st, surf...) is done at compile time, in the config.h file. Unfortunately any modification is silently erased at every upgrade.
I would probably fork the port, possibly include personal patches, customise the Pkgfile at will, and install the forked port instead. This, however, makes the upgrade process more cumbersome than it was since one does now not only have to `prt-get sysup` but also to pull the potential updates of the official ports into all of its personal ones and also upgrade them.
One option is to use the git driver for your ports (/usr/ports/drivers/git after installing opt/git). As far as I know it's not officially supported by CRUX, but once you have your ports stored as a git repository, you could theoretically keep a local branch with your patches to the official ports. After a ports -u, you could then merge your local branch with the upstream repo. Disclaimer: I don't do this. Ryan
participants (3)
-
David L. Craig -
Ryan Mullen -
Virgile Andreani