that sounds good.
it seems there's at least a couple of people that are interested in other parts of AST besides KSH, so focusing on KSH but keeping everything else too seems like a good compromise.

thanks

lefteris

On 11/02/17 20:29, Kurtis Rader wrote:
On Thu, Nov 2, 2017 at 7:47 AM, Eleftherios Koutsofios <e...@research.att.com <mailto:e...@research.att.com>> wrote:

    if the plan is to reduce this repo to just enough to build ksh93,
    I think it should be moved to a separate repo, since this is
    supposed to be all of AST.
    I don't know if anyone still uses the whole thing but I'd rather
    keep it whole.


I was leaning towards cloning just the components needed to build ksh93 into a new subtree. The existing directories would be left as is so that anyone who wanted to build the other AST commands could continue to do so. As well as build the ksh93 as it existed at the time the project was open sourced. The reason to clone the ksh93 related files is to make it easier to focus on only those pieces that would need to be modified to fix bugs, lint, code style, the build tool chain, add new features, etc.

    Glenn and Dave used to package up ksh93 and just the libs needed
    to build it,
    I can put that up as /att/ksh93 if there's interest. it's from
    2013, like the master branch of AST.


Thanks, but that's probably not needed. I've already spent a few hours to identify the bare minimum of the existing directories needed to build ksh93. See https://github.com/att/ast/issues/42#issuecomment-339186060 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_ast_issues_42-23issuecomment-2D339186060&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=w8fB702vkC3W-R3CrCrZ-z27uWBR8v2uNvO18rq1ia0&m=4g6BlPj_-xNH2F9qRa_jylqrCbjWTOpOuqKNsVpVArw&s=MZMC3eKhD-jJLd7bBP5qqeqffs26WUjzlVCyvCbKGpo&e=>

    the biggest issue I have with building AST isn't so much the
    legacy code, but the header file incompatibilities, and these
    arise from AST trying to replace system libraries with better
    versions.


Yep, that has been the source of problems getting it to build on BSD flavors (including macOS). With the help of a couple of other people we recently merged a change that seems to fix those issues. But it would be much better if we could eliminate things like the AST wchar.h header that wraps the system provided header.

--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank

--
E. Koutsofios
AT&T Labs - Research

_______________________________________________
ast-developers mailing list
ast-developers@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to