Skip to content

FEATURE - SWISH itself becomes a CPACK ? This becomes cpack_swish_examples? #1

@TeamSPoon

Description

@TeamSPoon

I sort of assume this project exists for several reasons:

SWISH administrators really want and need the HTTP Admin tools of ClioPatria

http://cliopatria.swi-prolog.org/admin/settings
http://cliopatria.swi-prolog.org/admin/configuration
http://cliopatria.swi-prolog.org/user/statistics
http://cliopatria.swi-prolog.org/help/http
http://cliopatria.swi-prolog.org/cpack/list_packages

Running SWISH and ClioPatria together makes a system that is far greater than the sum of those two parts. So myself, I LOVE this project's intent.

Despite so far not happening, this project serves to mitigate any incompatibility created by making SWISH a CPACK doesn't damage the actual SWISH Project.

We need a home for examples too "ClioPatria specific" to be in SWISH source management.

Anyway, I wanted to just point out what I think I knew and wanted to get further insight if there was more reasoning beyond the two above last reasons for not making the actual SWISH Project itself a CPACK (Since as far as I can tell it merely add the "applications" and "rdf" directories ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions