From owner-freebsd-ports Sat Feb 16 5: 1:12 2002 Delivered-To: freebsd-ports@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 287F937B417; Sat, 16 Feb 2002 05:01:07 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1GD14s74811; Sat, 16 Feb 2002 05:01:04 -0800 (PST) (envelope-from jwz@jwz.org) Received: from jwz.org (h132.128.meer.net [209.157.133.132]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id FAA74960; Sat, 16 Feb 2002 05:00:36 -0800 (PST) Received: from grendel.jwz.org (localhost.localdomain [127.0.0.1]) by jwz.org (8.11.6/8.11.6) with SMTP id g1GD0Kt20808; Sat, 16 Feb 2002 05:00:20 -0800 Message-ID: <3C6E57E4.7A5ADA37@jwz.org> Date: Sat, 16 Feb 2002 05:00:20 -0800 From: Jamie Zawinski Organization: my own bad self X-Mailer: Mozilla 3.02 (X11; N; Linux 2.4.9-13smp i686) MIME-Version: 1.0 To: Jeremy Lea Cc: "Jose M. Alcaide" , dougb@FreeBSD.org, freebsd-ports@FreeBSD.org, Ade Lovett Subject: Re: ports/34172: xscreensaver 4.00 problem with GNOME References: <3C6A2EF9.4C565D70@jwz.org> <20020213111916.B230@v-ger.we.lc.ehu.es> <3C6E1B7C.4B6C6F60@jwz.org> <20020216141654.B60480@shale.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jeremy Lea wrote: > > On FreeBSD we've done just that, although there was a little flamefest And there was much rejoicing. > when the changes where made to the port, because when --enable-gnome is > supplied to xscreensaver it moves the location of it's configuration > files. It's probably going to result in xscreensaver being patched to > always put it's files in the same place, because that way we don't have > to have the ugliness of working out where the files are before > generating a packaging list. > > What are your feelings on always putting the files in the same place? I don't care where the files get installed, really; that's usually a platform-specific religion (Solaris likes /opt, SGI likes /usr/freeware, etc.) When you're building your packages, just invoke ./configure with whatever --with-configdir you prefer. I think it's the right thing for the *default* to be to put it in the Gnome place on gnome systems, and in the X place on non-Gnome systems. But it's only a default... I don't know how the fbsd build system works, but I assume that somewhere you've got a script that invokes configure -- so you shouldn't need to patch xscreensaver itself, you just need to invoke configure with the args you like. -- Jamie Zawinski jwz@jwz.org http://www.jwz.org/ jwz@dnalounge.com http://www.dnalounge.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message