[openbeos-build-team] Re: Detecting libgcc

  • From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
  • To: openbeos-build-team@xxxxxxxxxxxxx
  • Date: Sat, 29 Jun 2002 12:35:14 -0400

There is also moving from the *OLD* format (the one I set up last Sept) to the 
new format.

>
>> I spoke extensively with Erik last night. 
>> He has the scripts nearly done and he is testing them on cdsoftware's 
>> CVS server to make sure that they are right.
>> He wants to release them to a limited audience to get a little more 
>> test time, then when we are all happy, we can check it it.
>> I know that this is taking quite a while. I wish I could see some way 
>> around that, but we certainly don't want to do this half way, or twice.
>
>Perhaps it's because I don't know the whole picture or because I'm just 
>ignorant, but I don't understand the fuss. As it seems to me, basically 
>the top level structure changes. And in my eyes this can be done, by 1) 
>forbidding CVS commits, 2) checking everything out, 3) moving the dirs, 
>4) CVS removing the old files, adding the new ones and commiting these 
>changes, 5) fixing paths and path related issues in files (e.g. the 
>stupid SubDir and SubInclude rules in Jamfiles (I strongly recommend to 
>replace them by ones that work dir-relatively) (a little script can to 
>that)) and commiting the changes, and 6) permitting CVS activity. For 
>those disliking empty directories -- personally I don't have a problem 
>with this as my .cvsrc specifies -P for co and up -- the Sourceforge 
>people can be asked to remove the old directories.
>
>... rather simple, but certainly I miss something.
>
>CU, Ingo (preparing for a rant ;-)
>
>
>
>




Other related posts: