Slashdot Mirror
GNOME 2.3.0 Ported, Ready For Testing On FreeBSD
Dan writes "The first of the GNOME 2.4 development releases is now available. Code named 'Mighty Atom,' this FreeBSD release includes quite a few new proposed modules. Those wanting to test this release should checkout the ``ports'' module per these instructions. Be sure to download the ``marcusmerge'' script from the same page. This script will help you merge the GNOME development ports tree into your main ports tree."
First?
HEADS UP TESTERS: GNOME 2.3.0 is now available for FreeBSD
c gi, and follow the
/path/to/checked/out/ports/tree -d /path/to/main/ports/tree
/home/marcus/src/marcuscom-cvs/ports -d /usr/ports
/usr/ports/x11/gnome2, and do a make install.
/etc/make.conf to aid in debugging:
:: marcus@FreeBSD.org
Joe Marcus Clarke says that his team has finished updating all the necessary ports for GNOME 2.3.0 (dubbed "Mighty Atom"). He is looking for people to test this pre-beta development release. Since it is a testing release, it does not appear to have been committed to the ports tree as of yet. Use this only if you are not looking for your desktop to be fully functional.
From: Joe Marcus Clarke
To: gnome@FreeBSD.org
Date: 13 Apr 2003 04:21:52 -0400
Subject: HEADS UP TESTERS: GNOME 2.3.0 is now available
Adam and I have finished updating all the necessary ports for GNOME
2.3.0. For those that did GNOME 2.1 testing, the procedure hasn't
changed. For new testers, you should go to
http://www.marcuscom.com:8080/cgi-bin/cvsweb.
instructions there to checkout the ``ports'' module. Then, download the
marcusmerge script from the same page. Then run:
marcusmerge -s
For example:
marcusmerge -s
This will merge all the development ports with your main ports tree.
From there, you can run portupgrade -ra (if you already have GNOME 2
installed), or cd to
Note, this is a _development_ release. That means pre-beta for the most
part. Only do this if you don't really care about your desktop
functioning most of the time. I also encourage you to add the following
to
CFLAGS=3D "-O -pipe -g"
STRIP=3D
There may be things broken with the port (i.e. forgotten dependencies,
missed files, etc.). If you notice anything, please report it to
freebsd-gnome ASAP. You probably shouldn't file PRs against these ports
as they won't be reflected in commit logs. However, if you notice
genuine problems with an application, don't hesitate to fire up
bug-buddy, and report the problem with the application authors.
Happy bug hunting!
Joe
--
Joe Marcus Clarke
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome
PGP Signature and some header removed because slashdot thinks they're lame.
guru in training
http://www.newamericancentury.org/iraqclintonlette r.htm
...
...
January 26, 1998
The Honorable William J. Clinton
President of the United States
Washington, DC
Dear Mr. President:
We are writing you because we are convinced that current American policy toward Iraq is not succeeding, and that we may soon face a threat in the Middle East more serious than any we have known since the end of the Cold War. In your upcoming State of the Union Address, you have an opportunity to chart a clear and determined course for meeting this threat. We urge you to seize that opportunity, and to enunciate a new strategy that would secure the interests of the U.S. and our friends and allies around the world. That strategy should aim, above all, at the removal of Saddam Hussein's regime from power. We stand ready to offer our full support in this difficult but necessary endeavor.
Such uncertainty will, by itself, have a seriously destabilizing effect on the entire Middle East. It hardly needs to be added that if Saddam does acquire the capability to deliver weapons of mass destruction, as he is almost certain to do if we continue along the present course, the safety of American troops in the region, of our friends and allies like Israel and the moderate Arab states, and a significant portion of the world's supply of oil will all be put at hazard. As you have rightly declared, Mr. President, the security of the world in the first part of the 21st century will be determined largely by how we handle this threat.
We believe the U.S. has the authority under existing UN resolutions to take the necessary steps, including military steps, to protect our vital interests in the Gulf. In any case, American policy cannot continue to be crippled by a misguided insistence on unanimity in the UN Security Council.
We urge you to act decisively. If you act now to end the threat of weapons of mass destruction against the U.S. or its allies, you will be acting in the most fundamental national security interests of the country. If we accept a course of weakness and drift, we put our interests and our future at risk.
Sincerely,
Elliott Abrams, Richard L. Armitage, William J. Bennett,
Jeffrey Bergner, John Bolton, Paula Dobriansky,
Francis Fukuyama, Robert Kagan, Zalmay Khalilzad,
William Kristol, Richard Perle, Peter W. Rodman,
Donald Rumsfeld, William Schneider, Jr., Vin Weber,
Paul Wolfowitz, R. James Woolsey, Robert B. Zoellick.
Oh the irony.
When are the slashdot dorks who continue this ridiculous BSD shit going to learn that it's not so much annoying as it is evidence of their complete and total loserdom?
You are a fucking nerd. Get a life.
Sorry to respond to this shit, but someone has to.
Your objections are duly noted.
I think that I have suceeded in annoying you, despite your claims to the contary.
In fact, no one need respond.
P.S. *BSD is dying.
Well, regardless of the trolls, and IMHO Gnome (And KDE) is too bloated for my tastes, it is still good to see the variety of platforms support for a common desktop environment.
I personally think that there are far too many librarys to compile, and then trying to find a list of order to compile libs/dependencys is hard on both KDE and Gnome's site(s).
I did eventually succeed in findy these lists and the order, but then I had trouble compiling them. I had this problem both with FreeBSD and Mandrake Linux.
So... Once again, am glad to see work in the open source community.
I will continue to use Fluxbox until E-17 is released or more useable.
For everyone else that likes to watch their Athlon systems chug away when loading Gnome or KDE, enjoy.
Oh yes, a flame... Linux kernel 802.11b support still sucks with 2.4.20, must use pcmcia-cs. Hmmm... BSD is dying but ever since I remember in July, 2001 FreeBSD and OpenBSD had great wifi support while linux was still dragging behind.
OK, you can flame me now trolls.
Privacy? Not in this lifetime.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It
It is always good to see applications progress on FreeBSD, but despite this I am quite happy to keep running Blackbox indefinately :)
Saying your OS is the best because more people use it is like saying MacDonalds make the best food
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a mere fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Wow! Gnome has been ported from RedHat Linux to FreeBSD! That's totally amazing.
Slashdot is jumping the shark. I'm just driving the boat.
Anything that is alive is in the proces of dying. If something is not dying, then it is not alive. All the fanboys who claim that *BSD is dying, but that thier favourite OS is not should ponder this.
I am TheRaven on Soylent News
wouldn't it be great if the BSDs and the Linux's could get along just long enough to produce one operating system where EVERYTHING is cross-platform? No more worrying about having to recompile my apps and source code fixes, no worrys about drivers not working, and support for all the devices combined? wouldn't that be nice? SO WHY THE HELL NOT!!!!!
I mean come on you guys, arguing which operating system is better is like the special olympics, even if you win you're still retarded. And its not going to get you anywhere to bicker about it either. Let the grand unification begin!!!!!!!
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
Is there ever going to be RPMs available for 7.3? I'm getting tired of compiling the entire GARNOME distribution for 7 hours every time there's a new release. I refuse to upgrade to 8.0 (Don't want "null' or whatever they call it, plus the other problems people have had). Plus Garnome's distribution of KDE is horribly broken - all of my text just shows up as dashes in every QT app.
A sentence you'll never see on an Internet discussion board: "You know what? You're right."