Great :-) I can't wait to see.
robert
On Tuesday 19 September 2006 17:37, Robert Baker wrote:
> Well I have about the same schedule as you Robert, but I am willing to
> throw my hat in the ring to help maintain HLFS-Stable. I have a big
> interest in seeing that we can work out a hardened s
Well I have about the same schedule as you Robert, but I am willing to
throw my hat in the ring to help maintain HLFS-Stable. I have a big interest in
seeing that we can work out a hardened system capable of being used for stable
server environments. I think that starting another branch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Day wrote:
>
> And then, when all these goals are reached, mark it as stable.
> The version will be stable for the exact
> versions/patches/desired_features(like SSP) done.
> And no matter what happens, never upgrade anything past the goal or
> a
For a stable project to happen, you should probably fight the urge to
make any kind of change whatsoever.
To do that, plan the entire project in a manner similar to the following:
1) Make a list of sources/projects/scripts/hacks/instructions that are
currently stable
2) Make a list of $(above) t
For the TODO list:
Solve testsuite bugs. These are almost always caused by one or more of the
compiler flags, and almost always only affect the testsuite. Glibc has
exceptions to this rule. Add -fno-flags to CC, CFLAGS, and/or
CFLAGS_FOR_TARGET during testsuites.
Compiler warnings often have pa
Robert Connolly wrote:
I'm sorry to say I'm much better being an hlfs-unstable maintainer than
hlfs-stable maintainer. I'd love to have hlfs-stable, but I never stop
finding things to break/fix :-) If releasing hlfs-stable is a priority then
it would be a good idea to create a second branch w
Hi,
>>> It's active, but I seem to be the only maintainer and I work 55 hours
>>> per week.
>> I don't have exactly *much* time either, but I'd like to help you. Alas,
>> I'm not much C-positive. So, first I'm going to study new HLFS features
>> and then I'll build to see how it goes.
> Well I'd l
It's active, but I seem to be the only maintainer and I work 55 hours per
week. There are several things I'd like to complete before a stable
release... stuff like fixing most of the compiler warnings, finding how to
get all the testsuites to pass, auditing the patches. The combination of gcc4
