[rkward-devel] How to deal with binary packages?
nono.231 at gmail.com
Fri May 1 07:25:06 UTC 2009
2009/4/30 Thomas Friedrichsmeier <thomas.friedrichsmeier at ruhr-uni-bochum.de>
> So how to handle this?
> 1) Upload all contributed packages to the sourceforge download page. In
> this is your favorite, there's a catch, though: I'd like to delegate most
> the work to another person. Making file-releases is a cumbersome process,
> already, and I don't want it to take up yet more of my time. Volunteers?
> 1b) Upload to a regular directory on an HTTP-server (like
> http://rkward.sf.net/temp/). Possibly slightly easier to handle, but still
> I'd like to delegate that task.
> 2) Have most packages hosted somewhere else, and simply keep a list of
> to those packages. Somewhat similar to
> in the new wiki). However, we'd probably re-organize this page a bit, and
> to make it more prominent (by advertising it as the primary download page).
> +1 for two. I made a few binaries for ubuntu because of the fast change of
rkward and R the last month and send a binary to somebody from the list who
asked for 64bit version. I do not consider my self packager, since the work
for debian was made. I just had the ubuntu and R version needed and compiled
Of course if somebody wants to build unofficial binaries nobody can stop
him. He can uploaded wherever he/she wants. I have seen that many times in
ubuntuforums for projects only with source that were somehow famous and
there were requests for binaries. But always these binaries were unofficial.
Another option is to have a list of people that can make binaries and their
distributions. So when the time comes for a release these people are
contacted and make also the binaries. These could help having official
binaries for rkward. This could work like the translation of rkward when a
new release is coming up there is a call. Just an idea.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rkward-devel