On Sat, 22 Nov 2014, Lennert Van Alboom wrote:

> On Sat, Nov 22, 2014 at 12:17:34PM +0000, David Mackay wrote:
> > On the topic of the Autotools: I do hope we will steer as far clear
> > from autotools as possible. CDE's build system is somewhat antiquated,
> > and a rehaul would be a prudent idea, but autotools is not
> > appropriate. In this day and age, with software projects abandoning
> > autotools en-masse owing to its complicated nature and a plethora of
> > technical faults, this would be a regression.
> 
> +1 for this part. 
> 
> While I personally don't really care much about the actual license CDE and its
> bits & bobs are under - I find GPLv3 to be restrictive enough to be 
> preferrably
> avoided, but I don't have code in CDE so it's not up to me to complain - the
> more permissive a license, the better, as far as I'm concerned. 

+1 here

First, to improve our support for unknown systems I'd propose
to fix many of #ifdef XxxArchitecture which got included
recently by yours truly. That brings us closer to better
supporting of new/unknown/strange systems.

For automated feature detection we might use iffe which afaik
is already in-tree by the graces of ksh93. Maybe we should
update our ksh before doing that (and maybe provide support
to build dtksh using already installed ksh library).

porting ksh93 to autotools might be a huge, lengthy and
largely unnecessary project....


//Marcin







------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to