|From:||"Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>|
|Date:||Sun, 3 Jul 2005 20:29:03 +0200|
Maybe in some future packaging/ports system where we can triviallyIt needs less than one man week to fix everything in ports/pkgsrc, not
edit vendor supplied sources we can put it back. But that time is
not now. As I said, we can't afford to spend man months messing around
with it, we have to move on.
included the build time. So we have now reached the stage where correctness
is less important than compatibility with broken programs?
I'm tired of this discussion. I won't comment the next time we have to change
something to conform to a standard which breaks existing software, I also won't
comment when we can't change something because existing software depends on
But keep in mind that software doesn't change when noone steps up to point out the problems and fix them.
When it's easier to
add bandaids, which have to stay forever, than to fix the underlaying problem,
something is wrong. When it is to complain, instead of investing the same time
to fix a problem, something is wrong. We choose to change our uname and to
stop pretending to be FreeBSD for a reason and that created problems. The situation
is not different at all from what we have know. Is the next step to revert that
-- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Description: This is a digitally signed message part