With all this back and forth about branching ksh away from AST so it can be 
more easily be built we may be losing sight on a bigger issue.  Right now many 
projected derived from some core AST functions have divergent versions of core 
libraries. The most obvious to me is cdt.  Container Data Types is used heavily 
throughout AST to handle sets, lists, associative arrays and more.  At AT&T we 
use it heavily in the vcodex/vczip data compression/transform system. It is 
also used by graphviz which is maintained externally to AT&T and AST now. 

In order to avoid having multiple versions of core AST libraries on a system we 
should really be looking at providing a method of building and packaging the 
libraries in a more standard way. Doing so would not only clean up the 
dependency version mismatches but may provide reasons for other projects to use 
the powerful libraries developed over the years. 

Personally, I’d like to see at least a CDT package (rpm or deb) and a vcodex 
package upon which ksh is built.  I believe the way most packages are done 
there would be two packages for all libs. One with the .so files and another 
with .a .h and man files. 

ASE


On 11/9/17, 2:39 PM, "ast-developers-boun...@lists.research.att.com on behalf 
of Siteshwar Vashisht" <ast-developers-boun...@lists.research.att.com on behalf 
of svashi...@redhat.com> wrote:

    
    
    ----- Original Message -----
    > From: "Siteshwar Vashisht" <svashi...@redhat.com>
    > To: ast-developers@lists.research.att.com
    > Sent: Friday, October 27, 2017 11:24:40 AM
    > Subject: [ast-developers] Branches in GitHub
    > 
    > Hello,
    > 
    > We are currently discussing the state of branches on GitHub[1]. I am 
thinking
    > about :
    > 
    > * Merging beta branch into master and do the development in master.
    > * Remove both alpha and beta branches. Commits from alpha and beta 
branches
    > can be tagged with respective git tags if required.
    
    
    I have created 2 new branches in the GitHub project:
    
    1. '2012-08-01-master' branch[1] contains the current master branch. It is 
the last stable release. I have cherry-picked one change[2] into it to allow 
building on Linux.
    2. '2016-01-10-beta' branch[3] contains last beta release and number of 
patches that were later added on top of it. I have forked it from last commit 
from beta branch before we started removing code.
    
    This should allow the old code to keep working.
    
    [1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_ast_commits_2012-2D08-2D01-2Dmaster&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2fZ9T41d9aranXLhOLJhmw&m=KFfowxv-ERrq1htS2FMBTt_jymJwDGirJJb9sd-WUFE&s=m6fG1MJQ-SfzBUjqpd9VkHhWuLN4MGsyysmn8MFW5oo&e=
 
    [2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_ast_commit_e79c29295092fe2b2282d134e2b7cce32ec9dcac&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2fZ9T41d9aranXLhOLJhmw&m=KFfowxv-ERrq1htS2FMBTt_jymJwDGirJJb9sd-WUFE&s=VEanmsPTNWgzONiczbTkjaKb6Docoj9dsPF4Q-yXj7U&e=
 
    [3] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_ast_commits_2016-2D01-2D10-2Dbeta&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2fZ9T41d9aranXLhOLJhmw&m=KFfowxv-ERrq1htS2FMBTt_jymJwDGirJJb9sd-WUFE&s=nJpoIAGsHZ17kEYv-vI7fbnhE3et__EBVIFI1I_sXts&e=
 
    
    
    > 
    > If you have any suggestions about it. Feel free to share it on GitHub or 
this
    > mail thread.
    > 
    > [1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_ast_issues_82&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2fZ9T41d9aranXLhOLJhmw&m=KFfowxv-ERrq1htS2FMBTt_jymJwDGirJJb9sd-WUFE&s=k1SmLzwwAEdN4HZ2fS0V_1vTI7ExN5JCrVkgrgDR5-Q&e=
 
    > 
    > --
    > --
    > Siteshwar Vashisht
    > _______________________________________________
    > ast-developers mailing list
    > ast-developers@lists.research.att.com
    > http://lists.research.att.com/mailman/listinfo/ast-developers
    > 
    
    -- 
    --
    Siteshwar Vashisht
    _______________________________________________
    ast-developers mailing list
    ast-developers@lists.research.att.com
    http://lists.research.att.com/mailman/listinfo/ast-developers
    

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

Reply via email to