Bug 118702 – app-portage/cfg-update-1.8.0-r2 (Update)

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description S. van Boven 2006-01-11 13:54:20 UTC]

Hi Harold,

Here's an updated ebuild... I have fixed a couple of things after receiving feedback on the forums:

1. It now correctly sets the executable bit after updating if the original file was executable.
2. It does not restore the MD5 checksum when restoring backups as that caused the file to be handled as unmodified even when it was modified because the wrong checksum was restored in the index... I found out that the original checksum can't be determined so I completely took this out. Restore files will be handled as modified files, forcing a manual update regardless of the true state of the file.
3. Added a variable to the cfg-update.conf that controls the GUI style of xxdiff.
4. Changed the indexing message to better match the style of emerge.
5. Removed the --fix option and moved the check for /root/.bashrc to the --on option. This has to be run manually after installation (because it changes a file in /root/)
6. Removed kdiff3 from RDEPEND in ebuild. Added text to the install instructions that a user can install different tools separately. xxdiff will remain the default tool.
7. Fixed reading of enable_backups setting from cfg-update.conf which was broken.
8. Fixed double printing of --help output
9. The .bash_profile and .Xdefaults file are no longer included in the tarball because putting the alias in .bashrc should be sufficient for using cfg-update.
10. Uploaded the updated tarball to my ftp server.

Thanks,

Stephan

[Comment 1 S. van Boven 2006-01-11 13:55:21 UTC]

Created attachment 76860 [details]
cfg-update-1.8.0-r2.ebuild

[Comment 2 Harald van Dijk (RETIRED) 2006-01-11 15:18:05 UTC]

Two very minor questions:

> 6. Removed kdiff3 from RDEPEND in ebuild.
kdiff3 was already never installed automatically regardless of USE flags, so I'm curious why that wasn't good enough. I don't mind either way though.

> ewarn "followed by running: alias emerge=emerge"
Any objections if I change that to "unalias emerge", or is there a specific reason for re-aliasing it?

I only took a quick look at cfg-update itself right now, but I don't see any problems with adding this new version, so I'll try to get that done today or maybe tomorrow, thanks.

[Comment 3 S. van Boven 2006-01-11 22:55:02 UTC]

Harold,

> ewarn "followed by running: alias emerge=emerge"
> Any objections if I change that to "unalias emerge", or is there a
> specific reason for re-aliasing it?
I simply didn't know about unalias... no problem if you change that.

I found another problem:
When the package is installed for the very first time, it doesn't have an checksum-index yet. This causes all updates to be skipped, but it won't create a checksum-index either if any updates are found...
So I must add a forced creation of the index when no index is found when running "cfg-update --on". This will make cfg-update show all updates as "modified files" and force manual updating.

I'll fix this tonight... Do you want me to bump to 1.8.0-r3 or simply change 1.8.0-r2 ?

I will add a force_index

The ebuild should add the file /usr/lib/cfg-update/checksum.index

[Comment 4 Harald van Dijk (RETIRED) 2006-01-11 23:53:06 UTC]

> I'll fix this tonight... Do you want me to bump to 1.8.0-r3 or simply change 1.8.0-r2 ?

Please bump it, thanks.

> So I must add a forced creation of the index when no index is found when
> running "cfg-update --on".

Shall I then remove "followed by cfg-update --index" from pkg_postinst for the new version, if this will be done automatically?

[Comment 5 S. van Boven 2006-01-12 11:18:57 UTC]

Created attachment 76926 [details]
cfg-update-1.8.0-r3.ebuild

Updated version...
Added forced checksum-index creation when running cfg-update --on
And did some minor changes to text messages due to this change in the sript.
Changed the ebuild accordingly.

[Comment 6 Harald van Dijk (RETIRED) 2006-01-12 12:10:47 UTC]

Added, thanks.