> It can be a difficult and onerous task to rebuild lots of server and
> client boxes up to a new distro version, or to try to integrate these
> into existing infrastructures and configurations when some features
> have changed (sometimes radically). To have some decent documentation
> available about what potential problems or other hiccups to expect
> would be absolutely invaluable.
>
> Please please please!
I would go further and ask programmers to mention their changes to source
code IN THE SOURCE CODE.
I've just been trying to build the latest bind on RHL 5.0; it built fine
on RHL 6.1, but gets lots of unresolved references on RHL 5.
Perusal of the patches did not show what they were trying to fix, and
there was nothing obvious. I tried excluding the glibc 2.1 patch to no
avail.
Finaly, I put together a script to
untar
build
while (more patchs)
{
patch
make clean all || exit
}
I have a prime suspect, but no idea what it's trying to fix. Nor any clue
about why it breaks things. I imagine it would have needed 3-4 lines of
comments, replicated (and maybe adapted) in each affected source file, and
that it would have added miniscully to the work in developing the patches.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
