Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Frank Loeffler <knarf@cc...> - 2009-03-12 15:10:24
I would like to make geoqo the tool of my coice, moving away from my own
collection of scripts, which would mean that I would probably also
contribute patches back. However, that means I also would like geoqo to
be a success and to be used by more than the number of users the mailing
list traffic suggests.
IMHO, the biggest problem of geoqo at the moment is the number of
dependencies on software which is usually not packaged for any given
distribution. I know of the Linux-binary thing and I think it is a nice
and neat way to circumvent that, but only for a short term. In
the end, users might want to change scripts for their own and 'build'
geoqo themselfes and they end up with the dependencies again. Also
running an elf-executable from somewhere on the web does not feel all
My point is: would it be possible and desired to try to remove some
of the non-essential dependencies, probably by including some of
the code of external modules into geoqo? I know that this basically
mean a code duplication, but in some cases the removed dependency
might be worth it. The ultimate goal would be to have geoqo included in
e.g. Debian. That would require all dependencies to be included as
well, and at the moment quite a few are missing - not packaged yet.