Re: gettext/GPLv4 virus infects FreeBSD

Begin <4866c611$0$17160$742ec2ed@xxxxxxxxxxxxxx>
On 28 Jun 2008 23:15:29 GMT, Paco <notforjdpspam@xxxxxxxxx> wrote:
jpd <read_the_sig@xxxxxxxxxxxxxxxxxxxxxx> wrote:
I don't understand where the "mid-release" comes from. Please
remember that the FreeBSD ports tree is not branched.
That is a policy failure.
No. It is a feature. If you don't like this feature, you can simply
not update your ports tree.

I couldn't have said it better if, well, if I was a RedHat plant being
paid to obfuscate criticism of serious flaws in a competing OS.

This sort of thing is why I stopped bothering to respond to you, or
in most cases, read your blatherings. We can do without the trolling.

You might find it easier jpd, by cutting down the time spent calling
those you disagree with trolls. In this thread alone name calling
accounts for over 50% of your contribution.

Har har. And you weren't? The previous time you pulled the exact same
trick. You run out of arguments, start calling people shills, and when
told that's no way to keep a discussion open and interesting, start
trying to accuse the person who just told you off of the exact same
things, except in a very special paco sauce.

I'm willing to accept that this is just that you are running into your
own limits here, but then it's time for you to accept that you were Just
Plain Wrong and move on to more productive things. Like, oh, trying to
be part of the solution instead of insisting on assigning blame.

We don't play the blame game here.

Well, most of us anyway. The thing is, we'd rather have a reasonably
working system than a lot of blame and no system. So bitching that it
doesn't work easily means you get handed the job of coming up with at
least a proposal or a design if not working code that does it better.

You have been invited to do so half a dozen times or so in this thread,
by various people. Pray tell, has your contribution to this very same
thread included at least 50% of constructive design discussion?


If you really do think the fact that FreeBSD ports maintainers are
volunteers somehow makes them off-limits for to criticism, no matter how
extensive the damage caused by their mistakes (from lack of understanding
of release management, lack of training, inexperience, or whatever)

You're mixing up a few things here, or rather, who said what. That and
forgetting that you can't threaten to fire volunteers. In fact, you're
even forgetting you're a complete outsider to the organisation and
nowhere near the people making policy. You do not have that say.

Neither do I, but contrary to you, I don't claim I do. I do know and so
I explained that this organisation, or rather, community, has a habit of
simply farting in the general direction of anyone who tries to pull fast
ones like you have tried to, and tried it rather ineptly at that.

You've been repeatedly informed of this and that you need to do better
to be taken seriously, yet you insist. Well, we'll just insist on not
taking you seriously. In this, previous attempts clearly show that you
have a better chance of getting the phone company to care.


then I'd guess that you don't have any children. If you did you would
know that both carrots and sticks are required, and expected, to properly
guide newbies.

There's always a few newbies that think their opinion trumps everything,
including the well-ment advice from people who clearly do know better.


If you really do know it all so much better, then start your own ports
replacement for FreeBSD and show us. Finding people who'll help you
with it is permitted, of course. I think you can recruit one or two
loudmouths right here. Come back when you're done. Feel free to gloat.

What exactly you expect to accomplish by such name calling?

Instead of what you claim, I told you to not try and call Philip names,
as they're transparant attempts to troll for reactions (shortened to
simply ``trolling'' in the vernacular, in case you weren't aware).

In the above paragraph I invited you to excercise your wisdom and
knowledge you seem to feel vastly superior to that possessed by the
entirety of the FreeBSD project, and fix the problems in a system
you blame on its creators' incompetence. In doing so, I apparently
``accomplished'' eliciting a reaction from you wherein you show yourself
functionally illiterate.


Well, it's all in a day's work, I guess. I must admit that I feel it
is a bit of a disappointment, altough not entirely unexpected, as it
seems to dash all hopes of a better world, or at least a better ports
collection replacement. Still, can't have everything, eh.


--
j p d (at) d s b (dot) t u d e l f t (dot) n l .
This message was originally posted on Usenet in plain text.
Any other representation, additions, or changes do not have my
consent and may be a violation of international copyright law.
.

Relevant Pages

  • Re: FreeBSD or OpenBSD
    ... > Should I make the switch from FreeBSD to OpenBSD for my servers? ... OpenBSD has proactively rabid security. ... negates the advantage of FreeBSD's larger ports tree for a server. ... Source upgrades (OpenBSD offers no official support for the ...
    (freebsd-questions)
  • Xorg 7.3 Works Fine Now - But .. A Few More Questions
    ... no longer being in he ports tree. ... Current Operating System: FreeBSD ozzie.tundraware.com 6.2-STABLE FreeBSD ... Module "ramdac" already built-in ...
    (freebsd-questions)
  • Re: Update Utility
    ... |>Subject: Re: Update utility ... |>> Is there any utility in FreeBSD 4.9 to check for possible updates/bug ... |>other than if you find a security advisory, you have to have the src ... |>since most daemons/applications are from ports, keeping your ports tree ...
    (freebsd-questions)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip
    ... started using freebsd and set up my first server. ... i personally do not trust binary package systems (although i am ... nor do i blindly trust the ports tree. ... a Changelog file, containing the history of major fixes/enhancements to ...
    (FreeBSD-Security)
  • How do YOU stay up to date?
    ... I'm finally getting my arms around FreeBSD and the updating processes ... I now understand how to use cvsup to keep my src and ports tree current. ... I know how to use pkg_add -r to install new sotware, ...
    (freebsd-questions)