| 1 |
On 08/11/2015 10:48 AM, Joakim Tjernlund wrote: |
| 2 |
> On Thu, 2015-07-23 at 08:47 -0700, Zac Medico wrote: |
| 3 |
>> On 07/23/2015 12:46 AM, Joakim Tjernlund wrote: |
| 4 |
>>> On Wed, 2015-07-22 at 19:47 -0400, Ian Stakenvicius wrote: |
| 5 |
>>>> |
| 6 |
>>>> Sent from an iPhone, sorry for the HTML... |
| 7 |
>>>> |
| 8 |
>>>>> On Jul 22, 2015, at 5:38 PM, Rich Freeman <rich0@g.o> wrote: |
| 9 |
>>>>> |
| 10 |
>>>>> On Wed, Jul 22, 2015 at 8:05 AM, Joakim Tjernlund |
| 11 |
>>>>> <joakim.tjernlund@×××××××××.se> wrote: |
| 12 |
>>>>>> |
| 13 |
>>>>>> There can not be any manual merges after an SW update here. |
| 14 |
>>>>>> |
| 15 |
>>>>>> I started to look at INSTALL_MASK, what if I set INSTALL_MASK |
| 16 |
>>>>>> to point to all conf files I want to manage myself. |
| 17 |
>>>>>> Then /etc/inittab etc. will not be touched when updating init |
| 18 |
>>>>> |
| 19 |
>>>>> This sounds like overkill. |
| 20 |
>>>>> |
| 21 |
>>>>> If you've already installed a custom /etc/inittab, then when you |
| 22 |
>>>>> emerge init, it won't overwrite your inittab even if you don't change |
| 23 |
>>>>> anything in your portage config. emerge won't touch any files in /etc |
| 24 |
>>>>> unless they don't already exist. |
| 25 |
>>>> |
| 26 |
>>>> |
| 27 |
>>>> ..AND have been modified. IIRC if the hash of the config files match what they were when the package |
| 28 |
>>>> was |
| 29 |
>>>> previously emerged, then the files are updated aren't they? |
| 30 |
>>>> |
| 31 |
>>>> I expect that this is fine in the situation described, but it's worth knowing that a config file left |
| 32 |
>>>> unmodified may be replaced with a different vanilla config file later on. |
| 33 |
>>> |
| 34 |
>>> Sure, but what if I need to change a conf file in an installed system? Or rebuild a a system from scratch? |
| 35 |
>>> The user only runs a one SW update command to update an installed system in the field and cannot edit a |
| 36 |
>>> bunch |
| 37 |
>>> of files too. Especially when there are hundreds of systems sitting in remote locations. |
| 38 |
>> |
| 39 |
>> If you use the profile-bashrcs profile-formats setting [1], then your |
| 40 |
>> profiles can use package.bashrc to define post_src_install and/or |
| 41 |
>> INSTALL_MASK to remove unwanted config files from upstream packages. |
| 42 |
>> Then you can easily replace the upstream config files with config files |
| 43 |
>> installed by your own configurations installed by your own ebuilds. |
| 44 |
> |
| 45 |
> Finally getting back to this after lots of distractions. |
| 46 |
> I cannot get profile-formats = profile-bashrcs to work. |
| 47 |
> I have in metadata/layout.conf: |
| 48 |
> masters = gentoo |
| 49 |
> profile-formats = portage-2 profile-bashrcs |
| 50 |
> then in profiles/tmv3-target-overlay/profile.bashrc: |
| 51 |
> INSTALL_MASK=xxxx |
| 52 |
> Doing portageq envvar INSTALL_MASK just yields an empty line |
| 53 |
> I guess I am missing something here? |
| 54 |
> |
| 55 |
> |
| 56 |
|
| 57 |
See the "man portage" for profile-bashrcs details. It uses |
| 58 |
package.bashrc rather than profile.bashrc, so that explains why it's not |
| 59 |
working for you. |
| 60 |
-- |
| 61 |
Thanks, |
| 62 |
Zac |
Archives