getting rid of mkproto.sh from Samba3

[Stefan (metze) Metzmacher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan (metze) Metzmacher schrieb:
> Gerald (Jerry) Carter schrieb:
>> tridge at samba.org wrote:
>>> Jerry,
>>>  > I don't want to start any flame wars on style so this is
>>>  > all I will say on the subject, but IMO all of your points 
>>>  > imply that autogenerated headers are better because they
>>>  > support bad programming habits.
>>> I see it as preventing programmer mistakes. If we had tools 
>>> to catch those mistakes, then the situation would be different.
>> I know.  There are valid points on both sides.  But it's the
>> lessons that hurt the most that we remember.  The current
>> mkproto.sh in Samba has led to bad programming habits and
>> monolithic code.  I doubt either one of us would disagree
>> on that.
> Hi Jerry,
> 
> Note: that in samba4 we start from the same code base (samba3)
> And a took a lot of steps to come to the current system
> (which hasn't reached it's last step yet!).
> 
> I think for samba3 the first step in this direction should be
> to restructure the code into subsystems and removing the
> autogenerated headers should be one of the latest steps
> and not the first one.
>

To make this clear, I don't propose to use the samba4 build system
in samba3, I just want to show what steps are needed to get
to a non-monolithic code base (and there're a lot of ways to
archive that...)

metze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGZpj4m70gjA5TCD8RAr9XAJwPosfyZ3uwQGMBBWnlkSw7mr5ZXQCgujlW
xcfnTH7EC1vilK+uFL6paIo=
=W631
-----END PGP SIGNATURE-----