Not that anything is set in stone yet, but I wanted to give you a
heads-up on packaging changes in Ruby that we (the Ruby SIG) are trying
to figure out.
The ultimate goal is to make Fedora the best development platform out
there no matter what it is exactly you target.
Core features of the current plan are:
- Use the alternatives system to point to one stack or the other for the
system default stack (think standalone applications).
- Enable running multiple different versions of the Ruby stack on one
system (e.g. 1.8.5, 1.8.6, 1.9.1 and possibly 1.8.7 and 1.9.2), as these
versions are still pretty current (think Enterprise Linux), pretty
easily maintainable (once we do it right) and very much needed -in
special cases :P
If you're interested in it's developments, which are targeted for Fedora
13, may I invite you to the Ruby SIG mailing list for a more detailed
The Ruby SIG mailing list is at:
One particular message of interest may be:
Phase two, write access with ACLs, is ready for testing. Please not
that URLs have changed since my original announcement.
git clone ssh://[fedoraaccount@]pkgs.fedoraproject.org/<package>
will get you a cone via ssh, in which you can git pull and git push.
The repos are the same from phase1, although I've done a few commits
here and there to test things. They are not tied to the CVS repos, so
changes you make here are truly throw away.
Please test cloning and writing to packages and branches of packages
that you would normally have write access to, or normally would /not/
have write access to. I'm interested in seeing both of those cases
Thanks again for your help in this project!
Fedora -- Freedom² is a feature!
According to this: http://lwn.net/Articles/367443/, latest kernel
updates have security fixes (the second one appears on the 188.8.131.52
Is this something that has been backported to current F-12 kernels (I
don't see it in changelog), or do we need a security update for F-12
I recently submitting Deja-dup, a backup program written in Vala for
Vala is described in more detail at http://live.gnome.org/Vala. Deja-dup
like many Vala programs include both the Vala source code and the C
"source code" to avoid a build time requirement of Vala and also because
Vala is still in a rapidly evolving stage. Do I need to build from the
original Vala source code or can I consider the machine generated C as