Re: DISCUSSION: Naming conventions (for C code)

Jaap Vermeulen (jaap@sequent.com)
Fri, 04 Jun 1993 09:02:29 -0700

I agree with Lance and Jose. Except... :-)

| Yes.. I would like to see it layed out like this for the source tree...
|
...
| python/lib/ /* This is where the libpython.a file gets put */
| python/include/ /* each makefile when given the "install" flag puts */
| /* "external" header files here */
| python/bin/ /* This is where the executables gets put */
| python/doc/
| python/samples/
| python/support/lib/ /* This is what the current 'lib' directory would become
*/

Here I disagree. The python libraries are true libraries and should be
treated as such. Therefore, they should be placed in
'python/lib/python' IMO. This would follow the same conventions as
'/usr' or '/usr/local'. (Picky, picky).

-Jaap-

--
Jaap Vermeulen					+--------------------------+
						| Sequent Computer Systems |
	Internet : jaap@sequent.com		| Beaverton, Oregon	   |
	Uucp	 : ...uunet!sequent!jaap	+--------------------------+