News for hackers. Stuff that matters.
Re:Packaging now standard, dependency proxy next? by ilaksh on Friday May 10, 2019 @08:58PM (#19883727)
I had no idea Gitlab already did this well before Github.

I think it's absolutely an appropriate response.

Re:Packaging now standard, dependency proxy next? by StavrosK on Friday May 10, 2019 @09:14PM (#19883814)
I use GitLab daily and for everything and I didn't know this. I know of the container registry and build artifacts, but they don't have an actual registry, do they? I can't point pip to something on GitLab and do "pip install mypackage" and it will work, correct?
Re:Packaging now standard, dependency proxy next? by scrollaway on Friday May 10, 2019 @09:23PM (#19883862)
It doesn't for python. It does for npm, java and docker though. I've been using the Docker one and it works fantastically well.
Re:Packaging now standard, dependency proxy next? by StavrosK on Friday May 10, 2019 @09:35PM (#19883918)
I use the Docker Registry as well, it does work great. Is there some special integration for npm/Java, or is it because you can just download the artifacts if you specify the URL?
Re:Packaging now standard, dependency proxy next? by scrollaway on Friday May 10, 2019 @11:00PM (#19884255)
There's an auth layer to implement + publishing APIs, I believe that's all there is though.

If only there was some standard for package hosting + publishing across all languages… stares at The Update Framework

Re:Packaging now standard, dependency proxy next? by skilled on Friday May 10, 2019 @09:02PM (#19883747)
This is the correct answer.