Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2001 13:06:14 -0500
From:      The Anarcat <anarcat@anarcat.dyndns.org>
To:        Jordan Hubbard <jkh@winston.freebsd.org>
Cc:        Libh <freebsd-libh@FreeBSD.ORG>
Subject:   Re: package tools
Message-ID:  <20011127180613.GA520@shall.anarcat.dyndns.org>
In-Reply-To: <1820.1006849763@winston.freebsd.org>
References:  <20011127045959.GA5828@shall.anarcat.dyndns.org> <1820.1006849763@winston.freebsd.org>

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

--2fHTh5uZTiUOsy+g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue Nov 27, 2001 at 12:29:23AM -0800, Jordan Hubbard wrote:
> > 2- Why "SYSINSTALL/" as meta-info directory? I mean, it's a bikeshed but
> > sysinstall is the installation program, which is not necessary related
> > to the package facilities. Is it realistic at all to challenge that
> > convention?
>=20
> Sure.  As you say, they're separate and were probably only associated
> at that level for convenience or because someone was confused.

I'll see what I can do.

> > 3- I will probably start working on basic package tools implementation
> > (pkg_*) to be complete before starting to work on a GUI. In other words,
> > I'll be hacking on pkgtools. In other words, I'm asking for
> > advice/permission/gotcha, etc. :)
>=20
> Sounds like a very reasonable place to start, though bear in mind those
> will probably be straight TCL scripts if you want to implement this the
> most direct way. :)

Indeed. They will be tcl scripts. Well, actually, they *could* be C++,
no?

> > 4- Have anyone explored the problems of libh/ports system interaction?
>=20
> I think at some point the ports collection could be mined for some exampl=
es
> of how to transition from the old package meta-data to the new, but that's
> so far along the line that I don't think it's really worth even looking
> at yet.

Hmm.. I don't know. Because in order to have packages to work with in
the first place, on *must* interact either with the ports collection, or
with the old package database, which comes back to the same issue, IMHO:
backwards compatibility.

Anyways, Alex has already written a makepackage.sh, so I don't think
it's too far-seeing. :)

a.

--2fHTh5uZTiUOsy+g
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjwD1hQACgkQttcWHAnWiGcHeACdEot/Ralv0IvmHC1WfXMJdA4C
i9YAn1o8oMTfN28fhn7JjGX+ss4yE+M4
=wziv
-----END PGP SIGNATURE-----

--2fHTh5uZTiUOsy+g--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-libh" in the body of the message




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