Date: Thu, 17 Nov 2005 14:15:23 -0800 (PST) From: James Long <james_mapson@umpquanet.com> To: dejan.lesjak@ijs.si (Dejan Lesjak) Cc: freebsd-x11@freebsd.org, Andy Fawcett <andy@athame.co.uk> Subject: Re: xorg-clients conflicts with xterm (patch) Message-ID: <200511172215.jAHMFNpI000954@ns.museum.rain.com> In-Reply-To: <200511172038.29727.dejan.lesjak@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
> [snip] > > ===> Installing for xorg-clients-6.8.2_1 > > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found > > ===> Verifying reinstall for xterm>0 in /usr/ports/x11/xterm > > ===> Installing for xterm-206_1 > > > > ===> xterm-206_1 conflicts with installed package(s): > > xorg-clients-6.8.2 > > And again, above is what confuses me - you don't have xorg-clients installed > yet so why would installing xterm complain about installed conflicting > xorg-clients. I wouldn't want to trouble you more but it would be interesting > to know the contents of /var/db/pkg at that time. I would surmise the conflict is because numerous other packages depend upon xorg-clients. So even though the package is temporarily missing, there are entries to it in the pkgdb dependency tree. Sorry, I don't have a snapshot of the /var/db/pkg/ directory at the time. However, the pkgdb -F output may show you what I mean about the dependencies. I don't mean to draw this out, I simply wanted to inquire about the Makefile syntax, and the fact that -- perhaps coincidentally -- editing out the ">0" and then doing a "make install" in xorg-clients made all my problems go away. There is also the untested theory that only portupgrade had a problem -- all my "conflict" messages come from portupgrade. Toward the end of my episode, since portupgrade had already build xorg-clients, but failed to install it, I went into /usr/ports/x11/xorg-clients, edited out the ">0" and was able to do a successful "make install" that installed xorg-clients and xterm. I thought the Makefile edit was what did the trick for me. Perhaps it was doing the manual "make install" that worked, and would have worked even with the stock makefile. Who knows. If the patch has no value, so be it. I just wanted to share what I had found that worked for me, again, perhaps just by coincidence. Jim Jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511172215.jAHMFNpI000954>