Please help: how to relocate installed files paths into an RPM database

[Matteo Pampolini]

Hello again Greg,

I tried your suggestion and it works, however, since it implies reinstalling
all the packages from their RPM files, though in database only, is no so
different from reinstalling them completely. If no standard solution is
available, I was looking for a sort of hack such as a query to manipulate
the database directly. I guess RPM development team should take this in
consideration because it allows a better portability of every RPM-based
installation.

Many thanks for your help,

Matteo

On Fri, Aug 7, 2009 at 5:30 PM, <Greg_Swift at aotx.uscourts.gov> wrote:

>
> > sorry for the delay of this feedback.
> >
> > Please excuse me but even reading many pages from the link you
> > suggested, things are still not clear to me,
> > moreover referred files seem to be related to an older version of RPM.
> >
> > Anyway, if I need to update the RPM database telling it that all the
> > *already installed* packages should be
> > found now on path B instead of the original one A, I guess I have to
> > pass this information to the command
> > I have to use, of course. AFAIK, I can do such a thing only during
> > installation of a new package, with the
> > relocation option, which is not my case. Even if I rebuild the
> > database, maybe deleting some existing files,
> > how can I pass this kind of info?
> >
>
> If I remember correctly you installed the rpm in this manner:
>
> rpm -ivh <package>.rpm --relocate /original/path=/your/path
>
> The only way I can think to change the entries in your rpm database is to
> remove the package from the database, and re-install it, but just to the
> database.  like this:
>
> rpm --justdb -ev <package>
> rpm --justdb -ivh <package>.rpm --relocate /original/path=/your/new/path
>
> Whether or not that will actually work as you expect it to, I am unsure.
> Just make sure to backup your rpm database beforehand.
>
> Unless someone wise than I speaks up, I believe that is the only way to
> accomplish what you want without figuring out how to manually edit the rpm
> database without corrupting it.  And I don't know that anyone would
> recommend that.
>
> -greg
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-list/attachments/20090812/5825e14d/attachment.htm>