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.

Sign up for GitHub

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

Jump to bottom

WIP: Upgrade PkgDev to a new 1.0 era #144

Closed
wants to merge 10 commits into from
Closed

WIP: Upgrade PkgDev to a new 1.0 era #144

wants to merge 10 commits into from

Conversation

KristofferC
Copy link
Sponsor Member

@KristofferC KristofferC commented Aug 15, 2018 •
edited by ararslan

Very WIP!

Fixes #145
Fixes #143

@KristofferC
Copy link
Sponsor Member Author

TODO:

  • Update commit message (include diff link)
  • Consistency check for registry
  • Update the PR code (perhaps use GitHub.jl)
  • Create a toy registry and ask people to try it out.

@KristofferC KristofferC mentioned this pull request Aug 29, 2018
Closed
@Nosferican
Copy link

What's the status on this?

@KristofferC KristofferC mentioned this pull request Sep 20, 2018
Closed
@dpo
Copy link
Contributor

dpo commented Sep 29, 2018

Bump. Currently BinaryBuilder doesn't build on 0.7 because of #143, which this PR should (?) fix.

@KristofferC KristofferC mentioned this pull request Oct 10, 2018
Closed
@StefanKarpinski StefanKarpinski mentioned this pull request Oct 10, 2018
Merged
@dpo dpo mentioned this pull request Oct 17, 2018
Closed
@ararslan ararslan mentioned this pull request Oct 18, 2018
Closed
bors bot added a commit to JuliaLang/Pkg.jl that referenced this pull request Oct 19, 2018
@bors @StefanKarpinski
Merge #814
fb99428 
814: code to (de)compress registry TOML files r=StefanKarpinski a=StefanKarpinski

@KristofferC, does this help you with JuliaLang/PkgDev.jl#144?

Co-authored-by: Stefan Karpinski <stefan@karpinski.org>
@KristofferC KristofferC mentioned this pull request Oct 22, 2018
Closed
@Nosferican
Copy link

Any updates?

@timholy timholy mentioned this pull request Dec 21, 2018
Closed
@mkborregaard
Copy link

When is this planned?

@tobanw tobanw mentioned this pull request Mar 14, 2019
Open
@davidanthoff
Copy link
Collaborator

Bump, would be awesome to have this :)

@davidanthoff davidanthoff mentioned this pull request Mar 15, 2019
Open
Nosferican
Nosferican reviewed Mar 16, 2019
View reviewed changes
README.md

[![Build Status](https://travis-ci.org/JuliaLang/PkgDev.jl.svg?branch=master)](https://travis-ci.org/JuliaLang/PkgDev.jl)[![Build status](https://ci.appveyor.com/api/projects/status/gnd6dqbdaxcx1c23/branch/master?svg=true)](https://ci.appveyor.com/project/wildart/pkgdev-jl/branch/master)

PkgDev.jl provides a set of tools for a developer to create, maintain and register packages in Julia package repository, a.k.a. [METADATA](https://github.com/JuliaLang/METADATA.jl).
PkgDev.jl provides a set of tools for a developer to create, maintain and register packages in a Julia package registry, for example (but not limited to) [METADATA](https://github.com/JuliaLang/METADATA.jl).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change this to General by now?

@KristofferC
Copy link
Sponsor Member Author

https://github.com/JuliaComputing/Registrator.jl is the future.

@mkborregaard
Copy link

But - does that also create a local package with the correct folder/file structure? Or is PkgTemplates the official recommendation for this?

@KristofferC
Copy link
Sponsor Member Author

KristofferC commented Mar 16, 2019 •
edited

Yeah, seems good for us to just make PkgTemplates the goto place for that

@adamslc
Copy link

adamslc commented Mar 29, 2019

For what its worth, I don't think that Registrator can completely replace the PkgDev workflow. Here is my use case: I maintain a small handful of private packages, and I maintain a private registry for these packages. I cannot publish the packages, even to a private GitHub repo. Currently, I manually update the registry, but I had hoped that I would eventually be able to switch to a more automated process. I strongly believe that I'm not the only one with these sorts of requirements.

Would there be opposition to me reviving this PR to try to get PkgDev into a usable state with the Pkg3 ecosystem?

@davidanthoff davidanthoff deleted the kc/07 branch November 16, 2019 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Nosferican Nosferican Nosferican left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
6 participants
@KristofferC @Nosferican @dpo @mkborregaard @davidanthoff @adamslc