Re: [gentoo-user] emerge hints needed

[Fredrik Andersson]

On Fri, Nov 20, 2009 at 6:44 AM, Dale <rdalek1967@×××××.com> wrote:

> Bill Kenworthy wrote:
>
>> Some time back I saw someone mention a way to get emerge to install an
>> ebuild with a bad digest - man emerge shows nothing so can someone give
>> me a hint.  It was much easier than going down the ebuild path.
>>
>>
>
> I think it is --digest.  I don't see it in the man page so you may have to
> do that with the ebuild command and the manifest option.  See man page to
> make sure.
>
> I will also add, you should not do this unless it passed the first test and
> you had to edit the file for some reason.  It could be corrupt or altered in
> some unknown way otherwise.
>
>
ebuild <path-to-ebuild> --digest


>
>  Also, I am in the process of rescuing a system from the
>> e2fs/util-linux/device-mapper snafu and find that now I have it booted
>> re-emerging util-linux wont overwrite the files I manually installed to
>> replace the missing ones - necessitating manually rm'ing some 50 or so
>> files - is there a way to force emerge to ignore file collisions and
>> just overwrite them in this circumstance?
>>
>> BillK
>>
>>
>>
>
> I think you are looking for this option with emerge:
>
>      --noconfmem
>             Causes  portage  to disregard merge records indicating that a
> config file inside of a CONFIG_PRO-
>             TECT directory has been merged already.  Portage will normally
> merge those  files  only  once  to
>             prevent the user from dealing with the same config multiple
> times.  This flag will cause the file
>             to always be merged.
>
> Keep in mind that it will replace whatever it emerges which may include
> dependencies.  I have never used that option before so be forewarned if it
> does.
>
> Hope that helps.
>
> Dale
>
> :-)  :-)
>