Timeline for Why prefer a package manager over a library folder?
Current License: CC BY-SA 4.0
26 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2018 at 21:30 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 146 characters in body
|
| Jun 27, 2018 at 14:38 | audit | First posts | |||
| Jun 27, 2018 at 14:38 | |||||
| Jun 23, 2018 at 19:59 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 204 characters in body
|
| Jun 23, 2018 at 19:53 | comment | added | jpmc26 | @SørenD.Ptæus Done. | |
| Jun 23, 2018 at 19:53 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 204 characters in body
|
| Jun 15, 2018 at 20:40 | comment | added | Ignacio Soler Garcia | I'm going to accept your answer if there is nothing new before Sunday. At least yours seems the best one to me. | |
| Jun 14, 2018 at 17:31 | comment | added | Damian Yerrick | Another case where your test environment's database server, version control server, and build server are all on a LAN is a shop in a rural area or developing country, where an Internet connection costs several dollars per GB. Often it's cheaper and faster to drive with a laptop to a hotspot in town to fetch updated packages for your local cache. | |
| Jun 13, 2018 at 13:56 | comment | added | Søren D. Ptæus | @jpmc26 Imho your first numbered list would benefit from some emphasis. | |
| Jun 13, 2018 at 11:20 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 120 characters in body
|
| Jun 13, 2018 at 10:28 | comment | added | Voo |
@jpmc26 Oh it was just one example. nuget.org was also down here for a few hours a while ago. You don't need a complete mirror, just a cache that keeps packages you already downloaded once locally. That way your builds will still work, which is nice if your whole dev setup relies on gated checkins. And you probably need a package repository anyhow for your own packages if they're not all public. As soon as you have that even the argument that you need the internet for a package manager goes away.
|
|
| Jun 13, 2018 at 10:12 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 108 characters in body
|
| Jun 13, 2018 at 10:07 | comment | added | jpmc26 | @Voo Keyword being "virtually." ;) I'm sure it does happen, but it's far from typical. Yes, I'm aware of left-pad. You're also aware that npm's maintainers stepped in, right? We could debate the ethics of their actions, but they clearly have a vested interest in keeping their system running and will take steps to mitigate bad actors. If you're Facebook or you're in an isolated network, sure, run a mirror. But for most dev shops, the risk is low enough, especially since most shops don't do daily releases or anything. It's a heck of a lot lower than someone screwing up when doing stuff manually. | |
| Jun 13, 2018 at 10:00 | comment | added | jpmc26 | @IgnacioSolerGarcia Creating a local repository is literally as simple as dropping files in a folder and dropping that path in a config file. I've done it with a network drive. Sure, you can get fancy and have a full blown hosted server if you want, but you don't have to if you need something quick and dirty or can't convince someone to spend the time/money on the hardware. | |
| Jun 13, 2018 at 9:58 | comment | added | jpmc26 | @IgnacioSolerGarcia Establishing a per project or per department or per company convention is not better than just having a convention everyone knows without being told. Additionally, the package manage does a better job of enforcing the convention, since it makes following the convention less work than breaking it. Also, as I mentioned, I commit NuGet directly and invoke it in the build script, so I don't need to have it installed. I keep build server installations to a truly bare minimum. | |
| Jun 13, 2018 at 9:29 | comment | added | Voo | Although having your own infrastructure is actually one of the few things that makes sense in any case: You don't want to be reliable on external infrastructure. If that one is not available for one reason or another it is much better to have a fallback that guarantees that your developers can continue to develop. (And before anyone tells me how that nuget.org or npm or <insert favorite package repo> would never ever have such troubles, maybe think again.) | |
| Jun 13, 2018 at 9:26 | comment | added | Voo | "Permanently developing without an internet connection is virtually unheard of" I wish I didn't know better. There's lots of development done in completely separated networks due to security reasons. Yes it is about as much fun as it sounds, but it is absolutely doable. You just have to set up your own infrastructure for package storage (i.e. your own nuget feed). | |
| Jun 13, 2018 at 8:32 | comment | added | Ignacio Soler Garcia | Well, I would love to respond to many points but this is too short. Summarizing, regarding 1 & 4 they can be easily solved by convention and regarding 2 that can be learned in 5 minutes with a document. I agree with some of your other points too, specially 5, 6 & 7. Regarding simpler environments people in this post tends to oversimplify the knowledge required. Talking about Nuget, it's UI, it's commandline options, the structure between solutions and projects, how to deploy the tool on build agents, how to create local repositories ... that's a nice amount of time ... | |
| Jun 13, 2018 at 5:10 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 329 characters in body
|
| Jun 13, 2018 at 5:03 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 1 character in body
|
| Jun 13, 2018 at 4:57 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 117 characters in body
|
| Jun 13, 2018 at 4:52 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 117 characters in body
|
| Jun 13, 2018 at 1:48 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 635 characters in body
|
| Jun 13, 2018 at 1:43 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 635 characters in body
|
| Jun 12, 2018 at 23:48 | history | edited | jpmc26 | CC BY-SA 4.0 |
added 108 characters in body
|
| Jun 12, 2018 at 23:42 | history | edited | jpmc26 | CC BY-SA 4.0 |
deleted 10 characters in body
|
| Jun 12, 2018 at 23:37 | history | answered | jpmc26 | CC BY-SA 4.0 |