jsizz

Why avoid recompiling? Why this reluctance to do a full rebuild?

I started programming in a world where you had to wait a day to get 300 lines of Fortran built. Now I routinely build the whole 44Gb of community ports of a major Linux distro in three days on a three hundred buck box at home.

There are 24 hours in a day, and your full rebuild will go just fine while you sleep, so long as you DON'T use -Werror.

Why can't developers, y'know, ACTUALLY READ THE BLOODY WARNINGS? And then, y'know, they could FIX MORE THAN THE FIRST ONE after a single build pass?

Three negative comments on this submission, that's some impressive anti-cult thing you've got going.

Slackware doesn't do "security theatre" updates. Whenever there's both a credible risk and a reasonable fix, you'll see an update, and it'll be quicker than distros that are multiple steps downstream from Debian.

Yeah whatevs. This reminds me of the ICL DAP with 1024 processors from 1979...

https://en.wikipedia.org/wiki/ICL_Distributed_Array_Processo...

> sometimes they cause problems (hello, Debian weak keys).

> until recently nobody was packaging Chromium for example.

To name one example, SlackBuilds.org has had Chromium since 2010, although admittedly that's not so long ago as the Debian weak key cockup, which was 2006.

Maybe your examples could use an upgrade to the latest stable version.

The planning authorities have an obligation to consider the potential historical and archaeological impact of a proposed development, and can impose an obligation on the developer for a professional archaeological investigation (funded by the developer) prior to construction, as a condition of approving the development.

Or in other words: "We know this site is teeming with archaeology. You don't get to trash it unless you pay for a proper dig before you start"

Yes, you're being ignorant. Use '--content-disposition' with wget, or '--remote-name' in curl. The top level directory in the tarball corresponds to this name and everything works out as expected.

And thus, every boneheaded project that ships with -Werror enabled will inflict an excrement tornado of FAIL on its grateful users and packagers.

THIS IS WHY YOU SHOULD NOT USE -Werror. NOT EVER. (And if you can't bring yourself to do anything about mere warnings, you shouldn't be in software engineering.)

Oxford Flood Network http://oxfloodnet.co.uk/ "Making a flood detection network in Oxford, using low cost sensors and volunteers"

Parloff spent years publishing pro SCO Group articles and pushing the undisclosed-Microsoft-patents-in-Linux meme. Do we spot a pattern here?

Thanks. FYI, for the upcoming 14.2 release we have an officially unofficial repo with hundreds of fixes for 14.2 ready to go (and hundreds more needed).

I'll admit I get a little tetchy when people insist on telling me 'xxx is broken on -current' when I already know exactly which 400+ packages are broken, and when everybody should understand that -current is for beta testers.

> I eventually left because slackbuilds.org was not being run very well and I couldn't get the packages I needed

I'd be interested to hear more about that if you're willing to share. Let's see if we can do something positive to fix it, even if it's too late to help you personally.

> I have never used a more convenient package manager than sbopkg before. Dependencies can be cleanly recorded and built with queuefiles.

http://idlemoor.github.io/slackrepo/index.html

It's worth pointing out that the Bernard S. Greenberg mentioned in the article in connection with NXSYS is the celebrated Multician who ported Emacs.

https://en.wikipedia.org/wiki/Bernard_Greenberg

"What makes Waterfox so fast? It's built with Intel's C++ compiler. One of the most powerful compilers out there. This enables us to make the fastest possible web browser for all the code changes we make. This potent combination makes for an unparalleled browsing experience."

Mm-Hm. How's that working out?

https://www.waterfoxproject.org/blog/ "Just a quick heads up why there hasn’t been any news from me in regards to the latest Firefox release. Mozilla have a new tuple header that they’ve created and gets used fairly frequently and unfortunately, this causes an internal compiler error as can be seen here." [Written by Alex Kontos November 9th, 2015]

Always a pleasure to count the number of clicks needed before you can establish that the only platforms are Mac and Windows.

So now Merriam-Webster has become the Twelfth Circuit? This is the lamest jurisdiction shopping I've seen in a while.

I absolutely do not agree with the idea that this is stealing. How can it be stealing, when the owner still has the thing that was supposedly stolen?

Different circumstances, different terminology. The correct terminology (see US Title 17 or CDPA 1988) is "infringing". Anyone who insists on using the word "stolen" is signalling their ignorance of the first, most basic fact of copyright law.

> What word would you use instead?

Infringing. (duh)

Please take a moment to actually read the Data Protection Act 1998.

http://www.legislation.gov.uk/ukpga/1998/29

75 matches for 'offence' on that page.

Sections 61 and 47 are particularly relevant. European data protection legislation really does have teeth, though the Commissioner has to have the will to use it.