🚀 go-pugleaf

If these bugs have already been discussed - then forgive me.
Does anybody out there have any good, easy, quick solutions 
to the following

1. If you include something like more than 6 or 7 libraries 
in you project (through the suitcase) and subsequently save 
the project, PB very nicely regenerates your Makefile. However, 
because it obviously thinks that the 'LIBS = ' line is too long 
it sticks a line continuation character in for you. Trouble 
is, it doesn't do it properly (leaves somes spaces) and the 
project wont make because the Makefile is corrupt. So you
have to edit the Makefile every time you save the project. No 
big annoyance but I could do without it. NeXT tell me its a 
hang on from 2.x and they intend to do nothing about it until 
next release. They suggest I write some awk/sed etc etc. I suggest 
to them that they write some awk/sed etc etc.

2. I work in a 6 person team. We are all writing the same application 
and therfore have a desire to share a project (as in Project 
Builder). However we can't because the .nibs can not be loaded 
into IB unless you are the owner. Yes, we are all in the same 
group (UNIX) and our Preferences permissions are set to rw-rw---- 
and our umask 002. What seems to happen is when the .nib is 
saved the permissions rw------- are set (for .nib and its files) 
without any reference to Preferences or umask. Now this is a 
MAJOR pain. A similar thing happens when you build a project 
and you're not the owner -a message 'fastcp : can not set network 
time.....etc etc' and falls over. 

What are the chances that no one has ever wanted to share a 
project before? I talked to another big NeXT site and asked 
them if they had similar problems. They told me they never tried 
sharing a project.

Anyway, if anyone knows of some good ways of dealing with these 
could you mail me?

Thanks in advance
David Lomax
uad1221@dircon.co.uk