| Re: [AD] Allegro generalization/extension mechanism |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro generalization/extension mechanism
- From: guilt <karthikkumar@xxxxxxxxxx>
- Date: Wed, 16 Mar 2005 11:18:46 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=NmM+0CM14739fuwWpsa4LLY0dXsgIQnetwoV8Bb3YMSrSmrgQeA6FfR6mCwFgMq9zVurJaQRk+IvKdtz/uOn+QpKjiTO+gjQkkKJSAvPSCK9Ly2Hmdf+D70oozVowVMjPHU5A1+OTxnHMlYesJaZblaorhPmE+lsQtuKVPa3diQ=
The average user will download the current project file of Allegro.
The project file (containing all the stuff) will be updated when the
core/implementations change much... So he will ideally be downloading
one big source distribution (which contains all the subprojects)
On Wed, 16 Mar 2005 16:02:05 +1100, AJ <aj@xxxxxxxxxx> wrote:
> guilt wrote:
> > So, this was the only point: only when it comes to releases, the
> > developer who wants the PNG code needn't wait for the next "stable"
> > update of the whole base to get his hands on.. the newer stable
> > release of the code will be available for download :)
>
> CVS is always available.
>
>
> > We can have major updates to Allegro this way by releasing only when
> > the core changes a lot.. :)
>
> the average user gets very confused by this.
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>
--
Karthik
http://guilt.bafsoft.net