On 02/05/2011 09:11 PM, Andreas Tille wrote:
> On Sat, Feb 05, 2011 at 07:38:12PM +0100, Manuel Prinz wrote:
>>
>> Creating some sort of "science bin/ directory" is IMHO just asking for
>> trouble. Also, if two scientific packages create a naming conflict, what
>> to do then?
> 
> Just for the sake of interest: Do you see any other problems than a name
> space conflict in the scientific field (which I just assumed for a
> moment when I wrote the proposal which is probably not very well
> thought).

This is a good question. My main concern is that Debian for some
reason or another may be perceived as incompatible by the scientific
community. If anything would require manual adjustments then we then
lose our edge in automated mass installs in clusters/clouds.

In general, the answer to this question mostly depends on how we
will interact in the upcoming years. We only do programs so far.
For those and for databases in particular what comes to mind
is that there may be discrepancies that would be preferred by
some sites - we do not know how to deal with multiple versions of
packages installed in parallel, yet. But this seems solvable, at
least for databases.

In my mind, to help collaborations best and help the community on the
way, we should strive towards limiting what we need to exchange between
sites. As much as possible one shall refer to standardised packages
across platforms and distributions to the degree that this is doable.
My working route towards that the Debian installation should be resembling
as much as possible the installation that a sysadmin would be performing
from upstream's sources.

It is a bit too early to tell. But with an increasing adoption of the
command line interface to the workflow tool Taverna, we will get
respective cross-platform efforts sooner than we think, I presume.

Many greetings

Steffen


-- 
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d4deb3e....@gmx.de

Reply via email to