RE: rpm port from FreeBSD / port behavior question

["Christian Gruber" <Christian.Edward.Gruber@gmx.net>]

Hmm.  Does this port integrate the rpm interface with the pkg_info system?
That would be mega cool if rpm on OpenBSD were a facade for the packages
system.

regards,
Christian.

-----Original Message-----
From: owner-ports@openbsd.org [mailto:owner-ports@openbsd.org]On Behalf
Of Andre Lucas
Sent: Monday, December 06, 1999 3:41 AM
To: Mike Hardy
Cc: ports@openbsd.org
Subject: Re: rpm port from FreeBSD / port behavior question



Mike Hardy wrote:
>
> Please, no holy wars about whether RPM sucks or not (I'm not sure if you
> have them, but I certainly don't want them) - I'm not in love with it or
> anything. However, I think its useful to have for peeking at how people
> built/packaged certain things when there's no *BSD port.
>
> For that reason, I think it may be useful to other porters, so here it
is.

Saved me the trouble of trying it, thanks.

>
> If anyone else has the time/inclination to upgrade rpm from 2.5.6 to
3.x,
> be my guest :-)

I was going to do a straight port (I did that for HP-UX with GCC, which
is a total bitch of an anvironment.) Has anyone tried that yet, with any
version of RPM? I'll probably have a go anyway...

>
> Here's a general porting question though: If I (as a porter) create
> certain directories that will contain very important program data,
should
> I delete them no matter what on uninstallation, or leave them there
> (possibly with a note)?
>

No! Even (un)InstallShield doesn't squash files that have changed. A
message would be best, but RPM's UI doesn't really provide much help
with that.

Though I think it's a useful tool, one of my main problems with RPM is
that you don't get much feedback on stdout, you have to check the logs
or read READMEs. Compare that to SD-UX on HPs, where you get almost too
much info... It's a tough balance to reach, I guess. I would like the
facility to write *important* messages to stdout once installation of
all packages is complete [or a reason why it's not :-) ] Please
enlighten me if that's already there, it's not AFAIK.

> To be concrete, imagine the RPM package database that gets built in
> /var/lib/rpm...If I upgrade RPM, I uninstall the old package, and then
> I've lost everything. Doesn't seem like polite behavior to me...

Exactly. However, RPMs are _supposed_ to be run in 'upgrade' mode, which
would give the app a chance to (e.g.) upgrade the DB to a new format. If
you erase the old package you are depriving the upgrade script of a
chance to do its magic.

Regs,
-Andre

>
> -Mike
>
>   ----------------------------------------------------------------------
--
>                  Name: rpm.tar.gz
>    rpm.tar.gz    Type: Unix Tape Archive (application/x-tar)
>              Encoding: BASE64

smime.p7s