From owner-freebsd-questions@FreeBSD.ORG Sat Sep 20 16:13:04 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64E4A1065674 for ; Sat, 20 Sep 2008 16:13:04 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 270F58FC22 for ; Sat, 20 Sep 2008 16:13:03 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 30C99AFBC03; Sat, 20 Sep 2008 08:13:03 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Sat, 20 Sep 2008 18:13:01 +0200 User-Agent: KMail/1.9.7 References: <48CFEC4B.1080009@optiksecurite.com> <200809161559.26614.lists@jnielsen.net> <48D11A72.5080301@optiksecurite.com> In-Reply-To: <48D11A72.5080301@optiksecurite.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200809201813.02053.fbsd.questions@rachie.is-a-geek.net> Cc: FreeBSD , John Nielsen Subject: Re: Multiple installation of one ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2008 16:13:04 -0000 On Wednesday 17 September 2008 16:55:46 FreeBSD wrote: > John Nielsen a =E9crit : > > On Tuesday 16 September 2008 01:26:35 pm FreeBSD wrote: > >> I've been asked by a customer to install Drupal on one server to manage > >> a new site. No problem yet. But, he also asked if it would be possible > >> to install it for other sites. > >> > >> I know that there is a warning if you want to install a port that is > >> already installed, but is there a way to bypass this? I know I could > >> install it from the tarball from the website, but I want to be able to > >> use portupgrade and portaudit to deal with it. > > > > I've done this in the past with Gallery and it looks like Drupal should > > be workable too. The thing to do is to make either a clone port or a > > slave port of the original and tweak a few things. In particular you'll > > want to add some sort of suffix to the port name and change the > > installation directory. > > > > For example, you could make a directory called ports/www/drupal6-custom= er > > and drop this in its Makefile: > > > > PKGNAMESUFFIX=3D-${CUSTNAME} > > DRUPAL_BASE=3Ddrupal6-${CUSTNAME} > > .include "../drupal6/Makefile" > > > > You could then do things like > > # cd /usr/ports/www/drupal6-customer > > # make CUSTNAME=3Dfoo install clean > > # make CUSTNAME=3Dbar install clean > > which would (with any luck) create independent installations of drupal > > under /usr/local/www/drupal6-foo and /usr/local/www/drupal6-bar. Or if > > you didn't want to worry about defining CUSTNAME all the time (or the > > desired name/location won't follow a predictable pattern) you could make > > a different slave port for each installation and hard-code the two > > values. I haven't tested any of this other than some quick verification > > of variables using make -V. > > > > HTH. If you have specific questions about port mechanics the ports@ list > > might be the best place to ask. See also the Porter's Handbook: > > http://www.freebsd.org/doc/en/books/porters-handbook/ > > > > JN > > That's a pretty interesting idea...I'll keep it in the back of my head. Good idea, but it's better to create your own 'local' ports outside of the= =20 standard hierarchy. For example, my own local ports reside in=20 ${PORTSDIR}/local. It needs one tweak in /etc/make.conf: VALID_CATEORIES=3Dlocal The reason it's 'better', is that you can maintain them in your own reposit= ory=20 and it's easier to make a tarball of all your local ports, rather then have= =20 them scattered over different categories. =2D-=20 Mel Problem with today's modular software: they start with the modules and never get to the software part.