[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 12 Feb 2002 11:40:17 -0800
On Tue, Feb 12, 2002 at 07:17:54PM +0100, Marcus Brinkmann wrote:
> > Hey Marcus - What do you want to happen with ifconfig in the next
> > release?
> You can put the code in, but disabled by default. We can put good
> use to it in the Hurd, but probably not on any other platform for
I think I'll leave it out for now (make dist doesn't have a good
option for having extra code lying around). The Debian GNU/Hurd
packages are likely to stay CVS-based for a while, so it's not
important to have it in this release.
In the next release, I want to have the ability to specify per-arch
which things should not be built (So the default will be to build
everything). That way ifconfig can be disabled as necessary (as well
as any other cleverness that eventually winds up in here).
> I have at least to add support to clear and set flags, and get some
> more system specific features in it (at least for GNU/Linux). I
> should take the time for this, but it would be stupid to delay a
> release for that. If I have the motivation, I might do it next week
> (unless you release before that).
My plan is to release on the 21st, although there doesn't appear to be
a good reason why I shouldn't release earlier if I can sort out the
cygwin build troubles. (I've figured out what's happening - when
configure adds items to the _PROGRAMS target, it's not adding
$(EXEEXT) to the binaries. I'm not sure what the Right Way to fix
this is yet).
This release is basically to get something that works out there.
I want to go live with the guy who came up with the phrase "Free like