xdg at mlists.thewrittenword.com
Thu Jul 15 15:52:23 EEST 2004
On Thu, Jul 15, 2004 at 09:37:25AM +0200, Alexander Larsson wrote:
> On Thu, 2004-07-15 at 06:19, Albert Chin wrote:
> > On Wed, Jul 14, 2004 at 08:49:47AM -0700, George wrote:
> > > On Wed, Jul 14, 2004 at 08:56:15AM -0500, Albert Chin wrote:
> > > > What case? That of someone installing a RPM for a different arch? Our
> > > > customers do this routinely. They might have a Solaris NFS server and
> > > > install packages for HP-UX, AIX, etc. on the Solaris NFS server with
> > > > rpm --ignoreos --ignorearch. It's much simpler than giving NFS root to
> > > > an HP-UX, AIX, etc. installation server for the corresponding arch
> > > > binary.
> > >
> > > Wouldn't then update-mime-database be installed locally on the Solaris NFS
> > > server and thus a solaris binary?
> > How does the HP-UX RPM know the location of the update-mime-database
> > binary on the Solaris host? RPM supports --relocate which is used to
> > perform the above installation so we have no idea where the Solaris
> > update-mime-database binary is.
> Eh, update-mime-database is hopefully in the path. How is this different
> from any other application launched in the rpm %post script?
For people installing programs to a _separate_ directory, there is no
guarantee that update-mime-database is in $PATH nor would it be the
correct version (say you want update-mime-database-1.0 or
The way we install software is different from the standard /usr/bin,
/usr/sbin, /usr/share/man, /usr/lib convention. We install programs to
separate directories so customers can upgrade to the newer release
when they want and possibly run multiple releases.
albert chin (china at thewrittenword.com)
More information about the xdg