Hello Everyone

One further point I haven't mentioned so far in this discussion thread is the establishing of clear 'development' and 'release' branches for GPC.  Aside from the necessity of separating the  work being done  on the GPC for  specific  features and major fixes, the release branch is an important tool for our community.

The release and development branches give this project developers a mechanism that provides them a code area within the project and the flexibility to work on features and add-ons that may be of interest to specific groups of users.

The release branch is where other developers and maintainers can work on GPC to improve stability, performance, and for managing patches and fixes when bugs are reported by the project's end-users.

The release branch also us all to know where the GPC has been, how long its  taken to reach a milestone or major development point and there can be separate release stages (alpha, beta, production) as is typical of other FOSS projects.

Prince Riley

On Wed, Dec 17, 2008 at 11:05 AM, Prof A Olowofoyeku (The African Chief) <chiefsoft@bigfoot.com> wrote:
On 17 Dec 2008 at 11:13, Kevan Hashemi  wrote:

> Dear Chief O,
> > Yes. You were worried about breaking your system gcc and your
> > existing gpc.
> Do you mean to say that you prepared this distribution specially for me?
> Now that's what I call service. Thank you very much.

You're welcome. :) I'm sure there are others with similar concerns (the
best option would have been to go for /usr/local/ - this is set during

> > You may need to set some environment variables in order for it to
> > work properly in a different location.
> Okay. I'll look out for that, fix it, and report back.


Best regards, The Chief
Prof. Abimbola A. Olowofoyeku (The African Chief)