Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Nov 2004 13:24:08 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Angelo Turetta <aturetta@commit.it>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: portindex -- the second coming.
Message-ID:  <20041102132408.GA96721@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <41877299.9090903@commit.it>
References:  <20041022153854.GA88362@happy-idiot-talk.infracaninophile.co.uk> <20041023111251.GA21742@happy-idiot-talk.infracaninophile.co.uk> <20041030225107.GA65879@happy-idiot-talk.infracaninophile.co.uk> <41877299.9090903@commit.it>

next in thread | previous in thread | raw e-mail | index | archive | help

--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 02, 2004 at 12:42:17PM +0100, Angelo Turetta wrote:
> Matthew Seaman wrote:
> >Slightly later than planned (real life getting in the way I'm afraid),
> >here's the third (and I hope final) beta version:
> >
> >    http://www.infracaninophile.co.uk/portindex/portindex-0.3.tar.bz2
> >
> >This incorporates various bug fixes and feedback from earlier versions.
>=20
> May I suggest trying to read as many settings as possible from=20
> /usr/local/etc/pkgtools.conf?
>=20
> I'm thinking mainly about MAKE_ARGS (that most often change the=20
> dependency lists of specific ports) and the various system paths:
>=20
> (quoting from pkgtools.conf)
>   #   ENV['PORTSDIR'] ||=3D '/usr/ports'
>   #   ENV['PORTS_INDEX'] ||=3D ENV['PORTSDIR'] + '/INDEX'
>   #   ENV['PORTS_DBDIR'] ||=3D ENV['PORTSDIR']
>=20
> The latter can (and should) also be set as make.conf or environment=20
> variables, but anyway the tool should take the issue into account one=20
> way or the other.
>=20
> The reason for this request is to simplify the maintenance of a single=20
> ports repository NFS-mounted from various architecures/OS versions.

Interesting idea.  I can't promise to implement anything like that
very soon, but I'll certainly keep it in mind.  Although it might be
easier to re-implement what I've done in Ruby and amalgamate it into
the portupgrade(1) suite.  As all the Ruby I know is from reading
(some of) the on-line 'Programming Ruby' book at www.ruby-lang.org I'm
probably not the best person to do that.

Making things like 'PORTSDIR' configurable is very high on the to-do
list: at the moment, the assumption is that the ports live in
/usr/ports.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBh4p4iD657aJF7eIRAhfgAJ0Tl0t+da7fijqazROo/WWSReq6/ACgruny
xmQUwMMVqCtXYlLjq3BFPZQ=
=iC6I
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041102132408.GA96721>