From owner-freebsd-questions@FreeBSD.ORG Wed Mar 29 14:23:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B3D16A422 for ; Wed, 29 Mar 2006 14:23:19 +0000 (UTC) (envelope-from spil.oss@googlemail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6550E43D9F for ; Wed, 29 Mar 2006 14:23:12 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: by zproxy.gmail.com with SMTP id v1so188301nzb for ; Wed, 29 Mar 2006 06:23:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ezOfHMih/jYa5DqGMp+pVcbVl/lR9pq/+1goaOb4HDoCIwVxSNTc9biplLiCisUSAMIg6ZSF9V86rxM87lxeudaPkfrHHTKSp5vHSXtLcUJPSr+m264ymf1qh9/sx3+bm9Iarac7BJuKNOSTM9rUmHkgVqcz7e7YKUr2eHL28ag= Received: by 10.36.84.19 with SMTP id h19mr1002620nzb; Wed, 29 Mar 2006 06:23:11 -0800 (PST) Received: by 10.36.128.18 with HTTP; Wed, 29 Mar 2006 06:23:11 -0800 (PST) Message-ID: <5fbf03c20603290623g33ccce0dy@mail.gmail.com> Date: Wed, 29 Mar 2006 16:23:11 +0200 From: "Spil Oss" To: "Alex Zbyslaw" , freebsd-questions@freebsd.org In-Reply-To: <442A9072.8070500@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5fbf03c20603290220l358768fy@mail.gmail.com> <442A9072.8070500@dial.pipex.com> Cc: Subject: Re: Incorrect inline documentation in /usr/local/etc/pkgtools.conf 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: Wed, 29 Mar 2006 14:23:22 -0000 Alex, Thanks a lot, that makes it very clear for me. Would it be a good idea to make that specific in the pkgtools.conf file? There must be more FreeBSD newbies that can run into the same trouble. Once I got a correct glob in, I could indeed see that the knob I had set was used. Thanks again, Spil. On 29/03/06, Alex Zbyslaw wrote: > Spil Oss wrote: > > >Dear all, > > > >Spent a lot of time trying to get portupgrade to install phpbb in the > >directory I want. > > > >Tried a lot of things, but only when I found out that ports_glob does > >NOT return anything on 'www/phpbb-*' I could fix it. > > > >The inline documentation in pkgtools.conf lead me to believe I had to ad= d > > MAKE_ARGS =3D { > > 'www/phpbb-*' =3D> 'WWWDOCROOT', > > } > >to my pkgtools.conf file to add it. > >[...] > > # e.g.: > > # MAKE_ARGS =3D { > > # 'databases/mysql323-*' =3D> 'WITH_CHARSET=3Dujis', > > # 'ruby18-*' =3D> 'RUBY_VER=3D1.8', > > # 'ruby16-*' =3D> 'RUBY_VER=3D1.6', > > # } > > > > > The short answer is that you want either 'www/phpbb' or 'phpbb-*' > > The 'directory/package' form matches against the directory structure > under /usr/ports. The directory you are after is 'www/phpbb'. > > The form without the directory structure matches against the installed > version of the package (I'm not sure how it finds it if the package > isn't installed, but I believe it does). > > You are probably being mislead by the "databases/mysql323-*" example, > as, at first glance, it looks like it is wildcarding against a version > number, like the following ruby examples, but it isn't. If you look > under /usr/ports, you will find directories like > "databases/mysql323-server" and "databases/mysql323-client" and it is > those directory names that the wildcard pertains to. > > I prefer the directory form, myself, because it tells me immediately > where I can find the package if I want to read the Makefile to find any > new or interesting knobs. > > Having said that, I have had occasional trouble in the past with > portupgrade refusing to recognise a directory in this format. > Specifically, I could not, for love nor money, get it to recognise > "www/apache20" and went with "apache-2*" instead. I have no idea if > this was a portupgrade problem or something obvious I was missing; if it > was a problem it might have been fixed by now. > > When building with portupgrade, you can clearly see when options are > picked up. Try re-installing a package for which you set knobs, and > watch the output. For any new items I add, I always check the output > carefully first time in case I made a typo or other snafu. > > --Alex > > >