Date: Mon, 14 Nov 2005 13:34:40 -0500 From: Mike Hernandez <sequethin@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: xterm conflicts with xorg-clients Message-ID: <20051114183439.GN31681@dementia.beyondnormal.net> In-Reply-To: <20051114182445.GA1884@flame.pc> References: <pan.2005.11.14.17.02.43.659160@io.dk> <4378C7C0.8080308@dial.pipex.com> <20051114174214.GH31681@dementia.beyondnormal.net> <4378D08C.2060103@dial.pipex.com> <20051114180730.GJ31681@dementia.beyondnormal.net> <20051114182445.GA1884@flame.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 14, 2005 at 10:24:45AM -0800, Giorgos Keramidas wrote: > New releases of xterm are made far more often than full X11 > releases, so it makes more sense I guess. Every time a new > version of xterm is out, you don't really need to download & > rebuild monster-tarballs with all the X11 sources. A simple > portupgrade invocation takes care of updating just xterm: > > # portupgrade -vuN xterm > > That's probably why it's a separate port. > Thanks for the quick and concise reply. It made sense to me to have the xorg-clients and server parts as separate pacakges, but I couldn't figure out why xterm would be alone. Now I have an idea :) Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051114183439.GN31681>