Slashdot Mirror

Most open source projects' commits are already gathered on cia.navi.cx. I don't see what ohioh can add besides a link to the real name, which is easy enough to find out anyway.

fyre http://fyre.navi.cx/ is quite cool as well

A short word about this. The right way to do this in a distributed environment IMHO is to use something like LLVM to ship binaries in a CPU architecture independent format. This has several advantages:

• LLVM images tend to be smaller than ELF images as the bytecode format is more compact than x86 code is
• The VM can produce native code without any virtual machine overhead at install time, whilst still optimising based on the CPU features available at runtime. This gives such binaries the same advantages that Gentoo users tout as being an advantage of compiling everything as all binaries are fully optimised for your CPU, but without the massive speed hit that C/C++ parsing implies.
• As new architectures are introduced there's no need to recompile packages, you can use the pre-existing ones after writing an LLVM backend
• The LLVM image format is quite good, and more easily extended than ELF. So things like relaytool become no longer necessary because we can fix it in the binary format rather than having to hack around it.

Nobody is working on integrating LLVM and autopackage right now though.

Neither does KDE. We have around 800 developers with 100 commits each on average. Although fairly it is mostly 200 core developers with 100s of commits. Check CIA/a.

What kind of fantasy land are you living in? Sure, if you are willing to dick about all day with apt pinning and use outdated software, maybe you can avoid it. It's a bit of a mission.

But if you want to use the latest versions of things, even if you use Debian you'll have to compile sometimes. Check out the users on the Ubuntu lists bitching about how Inkscape 0.41 just missing the upstream version freeze. Check out Fyre, a cool app for generating images from de Jong maps - note the lack of a Debian package. On Fedora far more software is not in the repositories than is.

Blind fanboyism won't get us anywhere. Even if the best case scenario, which right now probably means Ubuntu, there are serious problems with desktop software installation on Linux.

There is a lot of interest in solutions from users, developers and commercial ISVs (eg LSB/OSDL member companies). There are a few projects experimenting with new approaches, check out my own: autopackage, or Thomas Leonards Zero-Install.

In particular if you want to test Fyre, try the autopackage I made of it: Fyre 0.10svn. Both Fyre and autopackage aren't quite version 1.0 yet, but both are very close.

That build needs GTK 2.4. I have a build locally I will upload soon that adapts to the GTK features available at runtime (using relaytool) and therefore only needs GTK 2.2, but can still use the new file selectors and other features if they're available at runtime.

What kind of fantasy land are you living in? Sure, if you are willing to dick about all day with apt pinning and use outdated software, maybe you can avoid it. It's a bit of a mission.

But if you want to use the latest versions of things, even if you use Debian you'll have to compile sometimes. Check out the users on the Ubuntu lists bitching about how Inkscape 0.41 just missing the upstream version freeze. Check out Fyre, a cool app for generating images from de Jong maps - note the lack of a Debian package. On Fedora far more software is not in the repositories than is.

Blind fanboyism won't get us anywhere. Even if the best case scenario, which right now probably means Ubuntu, there are serious problems with desktop software installation on Linux.

There is a lot of interest in solutions from users, developers and commercial ISVs (eg LSB/OSDL member companies). There are a few projects experimenting with new approaches, check out my own: autopackage, or Thomas Leonards Zero-Install.

In particular if you want to test Fyre, try the autopackage I made of it: Fyre 0.10svn. Both Fyre and autopackage aren't quite version 1.0 yet, but both are very close.

That build needs GTK 2.4. I have a build locally I will upload soon that adapts to the GTK features available at runtime (using relaytool) and therefore only needs GTK 2.2, but can still use the new file selectors and other features if they're available at runtime.

then you should loak at this and this and this and ...

Take a look at [cia.navi.cx]
Combine a bot with CVS and you can do great things :)
(not talking about source-code pollution this would occur :D)

CAPTCHAs on edit? For instance: like this

Note: there are known issues with certain (rare) setups which have a non standard umask and X security settings. If you are on a stock Red Hat/Fedora install all should go smoothly (let us know if it does not). If you have tweaked your umask or have X security too restrictive (programs run as root must be able to connect) things will break.

If you want to test inkscape quickly and you are on x86 Linux, this is an easy way to do it. Just be careful. autopackage is in beta. If it breaks you get to keep the pieces.