FS#43281 - [devtools] updating devtools overwrites local config changes in /usr/share/devtools

Attached to Project: Arch Linux
Opened by Joakim Hernberg (jhernberg) - Wednesday, 31 December 2014, 16:31 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 04 January 2015, 17:30 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Updating devtools overwrites config changes in /usr/share/devtools

Would be nice if the buildscript got a backup array

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 04 January 2015, 17:30 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Flags exists to override configuration.
Comment by Dave Reisner (falconindy) - Wednesday, 31 December 2014, 18:15 GMT
This isn't the right approach. Files in /usr are never meant for site-local modification -- I won't add backup entries for them. If you need to maintain your own, do that, and invoke mkarchroot with the -C option and an appropriate path.

Out of curiosity, what sort of modifications are you making?
Comment by Joakim Hernberg (jhernberg) - Wednesday, 31 December 2014, 18:42 GMT
I mostly use the the extra and multilib scripts to build in a chroot instead of using makepkg directly. The modification I make is to add a 3:rd party repo (archlinux-production). I know that there are other ways to include dependencies not in the main repo, but using it this way turned out to be fairly painless. Maybe I go about it the wrong way, and I should override the config files somewhere else? I guess an alternative would be to add /etc/devtools and let config files there override the config files in /usr/share/devtools? It's just a bit annoying to have to update the config files when there is an update to devtools, but I suppose I could script something to do that fairly easily too.

In any case, an easy solution would be greatly appreciated :)
Comment by Dave Reisner (falconindy) - Wednesday, 31 December 2014, 19:21 GMT
I tend to think using the flags already provided by mkarchroot is pretty easy. Wouldn't you agree?
Comment by Joakim Hernberg (jhernberg) - Wednesday, 31 December 2014, 19:41 GMT
Beh, sorry about the form reload :S

I found changing the config files easier, but I guess I can write my own scripts to replace the devtools ones, or even easier a script that updates the config files when they've been updated. It's not like it happens all the time, and I suppose I'm probably the only one doing this.
Comment by Joakim Hernberg (jhernberg) - Thursday, 01 January 2015, 15:07 GMT
I suppose I'm in a vast minority in using devtools like this, so if you feel there is no merit in implementing the request, just go ahead and close it. Now that I figured out why my changes to the config files gets wiped, I can easily implement a solution locally.

Loading...