Date: Mon, 18 Mar 2002 17:37:15 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Kris Kennaway <kris@obsecurity.org>, Jochem Kossen <j.kossen@home.nl> Cc: Will Andrews <will@csociety.org>, freebsd-xfree86@lists.csociety.org, ports@FreeBSD.ORG Subject: Re: HEADS UP: XFree86 4.2.0 going back in the tree Message-ID: <p05101504b8bc19c9e5d0@[128.113.24.47]> In-Reply-To: <20020318134713.A67055@xor.obsecurity.org> References: <20020318004547.GA62117@jochem.dyndns.org> <20020318015837.GV53073@squall.waterspout.com> <20020318192807.GA22036@jochem.dyndns.org> <20020318205343.GO53073@squall.waterspout.com> <20020318205743.GA22186@jochem.dyndns.org> <20020318134713.A67055@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:47 PM -0800 3/18/02, Kris Kennaway wrote:
>On Mon, Mar 18, 2002 at 09:57:43PM +0100, Jochem Kossen wrote:
> > But...i WAS using portupgrade :-)
>>
> > (i did a portupgrade XFree86, and it chuckled on the
> > XFree86-4-clients port)
>
>So was I. Unless I'm mistaken, it deinstalls the existing
>XFree86-4 port during build (and puts it back at the end
>if the rebuild failed).
I suspect there is a timing problem for anyone who had the
4.2 megaport installed. If that is installed, then the
real sequence is this:
1) you effectively have all the sub-ports of the new
meta-port installed, *but* none of the package
programs realize this. They think you just have
an out-of-date version of XFree86-4.2
2) when you ask to update XFree86, the new meta-port
says "oh, but first I need the XF-libraries". It
then tries to build the "new" port of XF-libraries.
That port will make some decisions based on what
files *it* sees as being already installed.
3) the meta-port then says "I also need XF-clients",
so that port is made and installed. Again, that
port makes decisions based on what files it sees
as already being installed.
3a) repeat for all other sub-ports.
4) We then go back to "making the new version" of
the XFree86-4 port. Let's assume this works.
5) *Now* portupgrade will decide to delete the *old*
version of XFree86-4 -- the megaport. Assuming
it actually does this, it will be deleting files
which were installed by all the new sub-ports in
steps 2 and 3 (assuming those had all worked...).
6) Then, finally, it tries to do the 'make install'
for the new XFree86-4 port.
The exact details of the above may be wrong, as I haven't
gotten to the end of installing the new meta-port yet, but
I think the basic outline of the problem is accurate. The
current idea of deinstalling and re-installing a port does
not work if the new port is really several new ports, and
the old port is a megaport that had included all of those
pieces in a single port.
--
Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101504b8bc19c9e5d0>