Date: Mon, 2 Jun 2003 16:57:44 -0700 From: Will Andrews <will@csociety.org> To: Wesley Morgan <morganw@chemikals.org> Cc: kde@freebsd.org Subject: Re: [kde-freebsd] Re: HEADS UP: Big change to x11/kde3 (Read carefully!) Message-ID: <20030602235744.GD81874@procyon.firepipe.net> In-Reply-To: <20030602194350.O2676@volatile.chemikals.org> References: <20030602231303.GA28072@rot13.obsecurity.org> <Pine.LNX.4.44.0306021824010.29494-100000@pancho> <20030602233551.GC81874@procyon.firepipe.net> <20030602194350.O2676@volatile.chemikals.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 02, 2003 at 07:47:19PM -0400, Wesley Morgan wrote: > Then I would prefer a solution that was more configurable than 'minimal > KDE'. You have all the package names and your own set of variables in > bsd.kde.mk. Simply create a variable for something like "KDE_PACKAGES" and > default it to *all* packages. Those of us who don't want all can just put > a list of them in pkgtools.conf or /etc/make.conf .. This would improve > over the previous method as well. I'm no ports expert, but something > similar to what the 'gnomeng' does with package dependencies. > > USE_GNOME= gnomeprefix gnomehack gnomehier libwnck gnomedesktop > > Like that. At least, it seems like something similar would work here for > KDE. USE_GNOME isn't a user-adjustable variable. It lists dependencies of a port (that have to do with GNOME). Sure, you can specify WITHOUT_GNOME=<whatever> but if you don't HAVE_GNOME=<dependencies> of a specific port you can't install it. That aside... What is the point of having a variable like this, when you can just install what you want the first time around and let portupgrade upgrade them for you? It just adds needless complexity to the KDE ports. Regards, -- wca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030602235744.GD81874>