Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Mar 2004 02:20:52 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Ruslan Ermilov <ru@freebsd.org>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: RFC: doscmd removal
Message-ID:  <20040314102052.GA5663@xor.obsecurity.org>
In-Reply-To: <20040314101311.GB63843@ip.net.ua>
References:  <20040314022615.GA21795@cat.robbins.dropbear.id.au> <20040314052944.GA75355@zibbi.icomtek.csir.co.za> <20040314075329.GA3927@dhcp01.pn.xcllnt.net> <20040314082307.GA80283@zibbi.icomtek.csir.co.za> <20040314093143.GA4906@xor.obsecurity.org> <20040314101311.GB63843@ip.net.ua>

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

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

On Sun, Mar 14, 2004 at 12:13:11PM +0200, Ruslan Ermilov wrote:
> On Sun, Mar 14, 2004 at 01:31:43AM -0800, Kris Kennaway wrote:
> > On Sun, Mar 14, 2004 at 10:23:07AM +0200, John Hay wrote:
> > > > > > I plan to remove doscmd from the base system for the sole reaso=
n that it
> > > > > > is no longer useful. Any objections?
> > > > >=20
> > > > > Why would you want to remove it? It is still very usefull. I use =
it
> > > > > regularly. The only drawback currently is that the Makefile is set
> > > > > up in such a way that it does not pick up X during a "make world",
> > > > > so after a "make world" you have to build it again to pick up X.
> > > > > Built without X it is less usefull.
> > > >=20
> > > > This is exactly the reason why the source tree is not the right
> > > > place for doscmd.
> > >=20
> > > That might be and is the reason I asked for the reasoning behind it. =
One
> > > reason why keeping it in the tree is good, is because it help pick API
> > > changes that break it. Out in ports it might take a while to pick that
> > > up and then it will be the poor user's problem. :-/ Doscmd use parts =
of
> > > the kernel that isn't used by many other programs.
> >=20
> > Port compile problems are typically picked up on bento within a week,
> > and often within 24 hours.
> >=20
> No, the question was rather: how often the kernel gets updated on bento?

I build a new bindist for most builds, so the above still applies.  I
don't update the build machine kernels as often as that, but that's
not relevant for this discussion since doscmd isn't run with a new
kernel as part of 'make world', so runtime breakage of doscmd isn't
detected anyway.

Kris

--a8Wt8u1KmwUX3Y2C
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAVDIEWry0BWjoQKURAsm+AJ4mKa2qmyn9tWaxdZU0bsVVwU3LAQCggM5T
NWvJDrZF0Sd6Yk8+wtmlPFA=
=PF0R
-----END PGP SIGNATURE-----

--a8Wt8u1KmwUX3Y2C--



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