pax-hub / paxy Goto Github PK

Currently there is only one: Clone. Building an app with this singular instruction is quite difficult, so I think it's safe to say we need more step types.

Some examples might include:

• Copy - copy files from one location to another
• Command - run a shell command/shell script

Additionally, packages should be able to specify their own build steps. For example, when included as a build dependency, rust could have a cargo build step that runs cargo build in a given directory.

As you can see below, it is including files from the cargo registry in the home directory. We need to fix this somehow.

I'm not really sure why it's doing this.

Example. It is failing due to the lack of openssl dev packages

This should be implemented in the rm_repo.rs file.

1. Check that the repository name is in the file
2. If yes, remove it. If not display an error message

If the package is at file:///some/path/to/package.yaml, file://./flavor.yaml within it should be interpreted as file:///some/path/to/flavor.yaml

file:// URLs should never be able to target the user's local filesystem, and should only be allowed when there is already a relative base (as explained in #5).

Last release was almost 4 years ago.

Maintainer(s) seem to be completely unreachable.

Possible Alternative(s)

These may or may not be suitable alternatives and have not been vetted in any way;

• mach2 - direct fork