On Saturday, July 28, 2018 at 11:43:04 AM UTC-7, nafis wrote:
>
> Suppose I'm making a library and it does reference some other library not
> part of the standard library. I want to vendor those so that my library
> doesn't fail if the other 3rd party developer deletes their library or
> major
It is still there because someone if (hopefully) benificently name
squatting there with the same package. It went away and broke things.
The person who owns jteeuwen is not Jim (the original owner), and has
put back the go-bindata repo to avoid a breakage. It could be far
worse.
On Mon, 2018-08-13
IMHO
Don't do it for a library. Let your users decide if they prefer to commit
their vendor directory or not.
Do whatever you want for a standalone project.
JFB
Le samedi 28 juillet 2018 20:43:04 UTC+2, nafis a écrit :
>
> Suppose I'm making a library and it does reference some other library n
I have no idea what's going on there or the history, but I see
https://github.com/jteeuwen/go-bindata is still there, despite that "this
repository is not maintained".
On Thu, Aug 9, 2018 at 8:58 AM peterGo wrote:
> Tong Sun
>
> "I've never seen [the Author delete the library] happen before."
>
Tong Sun
"I've never seen [the Author delete the library] happen before."
It happened recently. Take a look at jteeuwen/go-bindata: Hard fork of
jteeuwen/go-bindata because it disappeared,
Peter
On Wednesday, August 8, 2018 at 10:01:32 AM UTC-4, Tong Sun wrote:
>
> I've never seen that happen
IMHO, the npm node packaging is just a mess -- I have several similar
projects, and each has to pull in a HUGE pile of almost-identical
dependencies, and not able to reuse between them at all. Whatever happening
over there will not astonish me at all, including the infamous
npm_left_pad_chaos
https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/
Manlio
On Wednesday, August 8, 2018 at 4:01:32 PM UTC+2, Tong Sun wrote:
>
> I've never seen that happen before, but in case it does, only new
> environments will fail, i.e., those has been building fine will still be
> building fine.
I've never seen that happen before, but in case it does, only new
environments will fail, i.e., those has been building fine will still be
building fine. I.e. it's quite easy to correct.
So I personally think that it is really a high price to pay for something
that may *never* happen.
Of cour
