Skip to content

Research Publishing Command Tools #3

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

Closed
flyingzumwalt opened this issue Jan 25, 2017 · 2 comments
Closed

Research Publishing Command Tools #3

flyingzumwalt opened this issue Jan 25, 2017 · 2 comments
Assignees

Comments

@flyingzumwalt
Copy link
Collaborator

Look up popular publishing tools like npm, git, etc and gather observations about how they work.

@flyingzumwalt
Copy link
Collaborator Author

@munadm

@munadm
Copy link
Collaborator

munadm commented Feb 11, 2017

There are some pretty cool ideas behind the different popular publishing managers out there.

All the well known ones (apt, npm, nuget, whatever they use in JavaLand) all follow the dependency tree format where a initial required root nodes is laid out by a parsable file (think of package.json) and then do a classic DFS of all the child dependencies of each root node. Many policies are being evolved to make this tree smarter and flatter. For example, apt employs the explicit versioning where you package needs to describe all the versions of the child dependencies you need straight off the bat while npm does actually tries to readjust the tree based on the full picture of all the dependency.

This is an important topic to explore when we will start developing our own publishing algorithm. Will profiles that have a cryptographic hash of their files need to show how files that have been cited from (think research papers with citation lists)? How about hashes of new versions of the data, how would we provide users a good experience when they want to know which version of the data has been cited?

As stated by the ticket here are some of the articles I've read to figure out some under-the-hood magic behind dependency management

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

No branches or pull requests

2 participants