Hi Steffen,
This email is very timely as at this moment I am trying to package the
server for Fedora/RHEL/CentOS. I don't think that the current source
tree limits this as it is possible to release multiple packages from a
single source. The issue it that the client and server will always be
released together and hence have the same version number. This
constraint is worth accepting for now in order to have a versioned
server package. As we move forward we should of course try to improve
the situation. For the Debian packages I have been in contact with
Gianfranco Costamagna.
Cheers,
Laurence
On 22/08/17 15:43, Steffen Möller wrote:
Hello,
We cannot distribute the BOINC server package in Debian since it is not
allowed to have code redundancy between packages of the distribution,
and be it for the source packages, so we cannot have the server and
client releases in parallel. The server side is on me, so this is
somewhat fine since I am happily busy on many fronts, but it is also
unfortunate as I think many good things could be achieved with a range
of short time projects. In particular I see it bringing BOINC closer to
wet lab environments who then provide proof of a prediction, which leads
to more BOINC-applying publications and respective promotion. Today,
with every client release the BOINC server package in the experimental
section must also be updated to avoid it being removed from the
distribution to avoid it looking outdated, but this then is from the
client source tree, not from the server one, so it is wrong.
When you now meet to rethink about how to organise the BOINC source tree
( refer to as set C of files) and have releases, please also have a
thought about how to have all the client needs (set A) separated from
what the server needs (set B) but the client does not (set B \ A). We
have the separation in A and B/A for the Debian BOINC server build
instructions (see
https://anonscm.debian.org/cgit/pkg-boinc/boinc.git/tree/debian).
There may be good reasons to keep both sides of the BOINC project in a
single source tree that I fail to see. Another way to get to something
consistent to distribute would then be to have regular releases of the
master branch, which is then have to be stable both for the BOINC client
and for the BOINC server.
Best,
Steffen
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
