From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: npm: ERR! cb() never called!
Date: Sat, 19 Sep 2015 04:28:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20150919T060922-696@post.gmane.org> (raw)
In-Reply-To: 55FB4347.6060508@gentoo.org
Michael Orlitzky <mjo <at> gentoo.org> writes:
> Heavy on bad words and light on solutions, but it made me feel better:
> http://michael.orlitzky.com/articles/motherfuckers_need_package_management.php
You know, when I read this I got quite a chuckle. Then I started to
'marinate' on this a while and stupid little things started to just
pop up in the back of my head. I've been trying to forget this post
ever since I read it; it has a bit too much truth to it, I suppose.
Then a bombshell hit me on a very big FOSS project (no do not ask the
name) that I could not believe I was reading.
It seems they have, somehow murky, all sorts of release tarballs with
proper identification, if you can find them with major.minor-revision
numbers, like we use in gentoo. But they pow_wow, pick the best one and then
release it with only major release numbers, although there are many, maybe
up to 5 or 6 tarballs floating around from the various work products
that should have the minor-rev info in the dam name.
So just spank my ass and send me home from coding school. How the hell can
they do that, and maintain any resemblance to credibility? Deep in the
ticket system you can find the details. Seriously, it's a joke and now
there's some finger pointing amongst some big names in 'open source'
development. I guess they just want folks to download major-distro binaries
and bolt ons to the various distros. What ends up in the distro binary
downloads is even a further drift from the sources. Some serious smoke and
mirrors.
So, Micheal's profanity, although not optimal, is ceratinly warranted.
The more I hack and write code the more I'm realizing that either idiocy
or chicanery is a mainstay of some major FOSS projects and the big distros?
Gut-wrencing experience, to say the least. I just can't believe folks this
smart that can code are such a bunch of fools............ Package manager?
These folks need a class in manners, ethics and common sense.
Rant on, Michael, Rant on!
hth,
James
next prev parent reply other threads:[~2015-09-19 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 14:03 [gentoo-user] npm: ERR! cb() never called! Alan McKinnon
2015-09-17 18:50 ` Michael Orlitzky
2015-09-17 19:24 ` Alan McKinnon
2015-09-17 20:53 ` Alec Ten Harmsel
2015-09-17 21:13 ` Alan McKinnon
2015-09-17 22:48 ` Michael Orlitzky
2015-09-18 6:57 ` Alan McKinnon
2015-09-18 8:19 ` Neil Bothwick
2015-09-19 4:28 ` James [this message]
2015-09-18 3:34 ` Alec Ten Harmsel
2015-09-18 7:05 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20150919T060922-696@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox