[haiku-development] Re: Removing legacy build platforms and -nostart
- From: Joseph Prostko <joe.prostko@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 18 Dec 2012 16:31:07 -0500
On Tue, Dec 18, 2012 at 6:22 AM, "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
Hey, Axel!
> On December 18, 2012 at 5:00 AM Joseph Prostko <joe.prostko@xxxxxxxxx> wrote:
>> proceeded. For example, I thought doing an annotated tag of something
>> like "lastBeOS" with a tagging message of "Last revision to support
>> BeOS as a build platform" would work well...
> What would be the purpose of tagging this revision?
Well, if we tagged it, we would know for certain that anything after
it would absolutely break BeOS as a build platform as a result. I'm
talking about removing BeOS from the configure script, getting rid of
nostart, and then removing __BEOS__ instances from the Haiku code.
> Is it confirmed that we actually still can build Haiku on BeOS?
No, it isn't so I see your point here. If building Haiku on BeOS is
already broken, it would be a bit pointless to incorrectly tag the
source as "lastBeOS".
> In any case, IMO it's being dropped as it has no value anymore -- a tag would
> therefore be useless as well, no?
I suppose so, as it would only be useful if BeOS can still build Haiku
today (I'm not sure), and if anybody actually plans on doing a BeOS
build ever again. If there are any people, I doubt there are very
many.
- joe
Other related posts:
