Skip to content

Discussion: Package manager inspired by pacman (Arch Linux) #3896

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
EmilCataranciuc opened this issue Feb 6, 2020 · 2 comments
Closed

Discussion: Package manager inspired by pacman (Arch Linux) #3896

EmilCataranciuc opened this issue Feb 6, 2020 · 2 comments

Comments

@EmilCataranciuc
Copy link

I know this has been previously discussed already but at least I need some clarifications.
First of all, it is not yet clear to me how would deno manage dependencies in a clear, transparent way? So that a developer could open one file and see the dependency tree.
Second, in it's current form, pulling packages from URLs isn't very redundant. If the server goes down you are dead in the water. Why not implement a package management similar to packman on Arch Linux (of course there are other similar package managers). Which pulls the package from a list of repositories provided either by the distribution or by the user.

@kitsonk
Copy link
Contributor

kitsonk commented Feb 6, 2020

First of all, it is not yet clear to me how would deno manage dependencies in a clear, transparent way?

deps.ts is a good convention... but it should be a convention, to allow people to have different conventions.

So that a developer could open one file and see the dependency tree.

You don't get a dependency tree with a package.json, but still the capability is already built into Deno

deno info main.ts

Second, in it's current form, pulling packages from URLs isn't very redundant. If the server goes down you are dead in the water.

If the registry goes down, you're dead in the water. What makes a formal priority package registry special to a web server? Again it is discussed in the manual as well.

Which pulls the package from a list of repositories provided either by the distribution or by the user.

At the end of the day, those are URLs to servers. Not any different from having that exist in code.

@EmilCataranciuc
Copy link
Author

Cool. Thank you. Looks like the documentation actually addresses many things already. Will keep reading it.

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