Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

atpkg support for binary atpm #30

Merged
merged 1 commit into from Jun 30, 2016
Merged

atpkg support for binary atpm #30

merged 1 commit into from Jun 30, 2016

Conversation

drewcrawford
Copy link
Contributor

See AnarchyTools/atpm#1

This commit adds

  • Dependency type to ExternalDependency, to distinguish between Git and Manifest types
    This design was settled on after looking at several, including autodetecting git (which is possible via git ls-remote)
    However, manifest ExternalDependency is quite different than Git ExternalDependency for several reasons (including the use of channels)
  • Channels, which are essentially like micropackages inside a package. A channel lets us say "stable" "beta" "linux" "osx" "swift2.2" etc. All releases are part of a channel. It would be possible to use separate manifests for each channel, but this would require the use of multiple manifests for basic osx/linux packages, which is undesireable
  • Tokens can now start with numbers, which is important, as we now have syntax where :1.0 { :url "https://example.com/some/tarball.xz"} is used to define where some version can be located

@drewcrawford drewcrawford changed the title WIP: atpkg support for binary atpm atpkg support for binary atpm Jun 7, 2016
See AnarchyTools/atpm#1

This commit adds

* Dependency type to ExternalDependency, to distinguish between Git and Manifest types
  This design was settled on after looking at several, including autodetecting git (which is possible via git ls-remote)
  However, manifest ExternalDependency is quite different than Git ExternalDependency for several reasons (including the use of channels)
* Channels, which are essentially like micropackages inside a package.  A channel lets us say "stable" "beta" "linux" "osx" "swift2.2" etc.  All releases are part of a channel.  It would be possible to use separate manifests for each channel, but this would require the use of multiple manifests for basic osx/linux packages, which is undesireable
* Tokens can now start with numbers, which is important, as we now have syntax where `:1.0 { :url "https://example.com/some/tarball.xz"}` is used to define where some version can be located
@drewcrawford drewcrawford merged commit 09f4704 into master Jun 30, 2016
@drewcrawford drewcrawford deleted the binary-releases branch June 30, 2016 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant