Skip to content

Improving "installability" of packages with compiled parts #5365

Open
@fingolfin

Description

Right now to install GAP packages, one basically has to copy the whole package directory, after building the package (or alternatively: install it, then build it in-place; that might be the only option if the package hardcodes its build path ... though ideally packages shouldn't do that).

Anyway, doing that means that .o files and other build artifacts are installed, which is undesirable.

Ideally one would be able to just install the required parts (documentation, GAP code files, possibly a kernel extension or external binaries), but leave out e.g. Makefiles, logs, .o files, etc.

Some constraints:

  • any such "install support" for packages should not impede the use of packages with "not installed" GAP.
  • packages w/o compiled code should IMHO not be forced to do anything (IMHO it ought to be fine to just copy them wholesale into something like PREFIX/share/gap/pkg/PKGDIR or so

There are multiple ways to achieve that, requiring different amounts of work and/or cooperation by package maintainers. I don't have time to go into details right now, but I wanted to have an issue I could reference people to in the future. (If others wants to explain their ideas how this could be achieved here: fine by me).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    topic: packagesissues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions