65 years ago today, the first industrial batch of plutonium was produced.
Element 94 was first synthesized in 1940 by a team led by Glenn T. Seaborg and Edwin McMillan at the University of California, Berkeley laboratory by bombarding uranium-238 with deuterons. McMillan named the new element after Pluto, and Seaborg suggested the symbol Pu as a joke. [...] The entire plutonium weapon design effort at Los Alamos was soon changed to the more complicated implosion device, code-named "Fat Man." With an implosion weapon, a solid sphere of plutonium is compressed to a high density with explosive lensesââ¬âa technically more daunting task than the simple gun-type design, but necessary in order to use plutonium for weapons purposes.
"Fat Man", as you may know, was subsequently dropped on Nagasaki, Japan. Perhaps it contains some revealing truth about mankind, that when we finally make reality out of the alchemical dream to change material from one element to another, we use it not to create beauty or riches, but to wipe cities off the face of the Earth.
❦
Okay, switching to the installed-modules branch. (If you're coming in through non-linear time, you might want to read what I did yesterday first.)
$ ./proto
*** CONFIG FILE TOO OLD ***
Hello, faithful proto user. Since the August 2009 release, Rakudo installs
and runs outside its source directories. It's time for proto to make projects
install Perl 6 projects in a similar way. Rather than spend a lot of effort
trying to guess how to upgrade our userbase from distributed to merged, we'll
just deprecate the old ways and let you do a bit of the work. Hope it's OK!
So here's the thing: we're moving to a model where PERL6LIB becomes optional
or needs to point to only one library base directory. You should probably
reinstall the projects you have already, so that they end up in that place.
Here are your currently installed projects ('legacy' in projects.state):
november html-template druid perl6-examples uri web svg svg-plot maya form pun io-prompt wtop xml statistics-lite json faz http-daemon yarn ppm epoxy epoxy-resin grampa csv perl6-literate perl6-sqlite mwbot
When you're ready to go with the new ways, please remove your old
config.proto and reinstall the above projects.
Ok. Bravely going where no man has gone before. Save for mberends++, and probably viklund++, and moritz++...
I remove config.proto.
$ ./proto
*** CONFIG FILE CREATED ***
Greetings! I have created a file '/Users/masak/gwork/proto/config.proto'
that you may want to review. Next time you run ./proto
these settings will be used to bootstrap your Perl 6 software ecosystem.
If you're new to this, or reluctant to do configuration, you probably want
the default settings anyway. The most important ones are:
Perl 6 executable -> /Users/masak/gwork/rakudo/parrot_install/bin/perl6
Perl 6 library -> /Users/masak/.perl6/lib
Looks good. Proceeding.
$ ./proto
Building proto...done
don't know how to parse the line ë state: legacy: /Users/masak/gwork/novemberû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/html-templateû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/druidû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/perl6-examplesû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/uriû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/webû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/svgû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/svg-plotû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/mayaû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/formû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/punû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/io-promptû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/wtopû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/xmlû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/statistics-liteû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/jsonû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/fazû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/http-daemonû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/yarnû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/ppmû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/epoxyû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/epoxy-resinû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/grampaû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/csvû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/perl6-literateû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/perl6-sqliteû, ignoring it
don't know how to parse the line ë state: legacy: /Users/masak/gwork/mwbotû, ignoring it
Now, that's not very pretty. The error is coming from lib/Ecosystem.pm:126. It's caused by the fake YAML parser not recognizing more than one word after the first colon.
Ah, this is the TODO point recording this piece of data format.
10. Drop the migration plan for existing installations: laziness++ ;)
Just warn the user as long as the old config.proto has not been
upgraded, and record as "state: legacy: /path" in projects.state.
This must be overwritten if the user later re-installs the project.
[DONE]
Need to talk to mberends++ about how to solve this. My guess is that we need to make the fake YAML parser a bit smarter, but even that might come at a cost.
mberends++ and I had a brief meeting on #perl6, and arrived at a solution which didn't involve messing with the parser.
So, now things work, and are much less noisy.
Re:Installed-modules branch
masak on 2009-11-07T03:27:09
Well, not running away screaming would be a good start...
:) Don't know if you've found mberends++' excellent list of TODO points in the proto script in the branch. Essentially, making the branch ready for merge comes down to finishing the points on that list.
