Re: R-Surveillance (Was: [med-svn] r3007 - trunk/packages/R/r-cran-surveillance/trunk/debian)
Hi Andreas,
Andreas Tille wrote:
[...long email...]
> As a technical compromise I would think about a link to pkg-escience
> as external SVN source which provides a direct connection. What
> do you think?
we have it this way for biojava. as a compromise from my side: we do it conversely? If I
don't need to do it myself, please feel free to move (or have moved) the packages
currently residing in pkg-escience to anywhere in debian-science, pkg-scicomp, debian-med
or pkg-java. A note on the Wiki page indicating where a package has ended up would be fine.
Those listed on the Debian-Med project page should be listed in "red", not in "yellow".
The latter would indicate that the package is current and functional. The packages _may_
be functional, but they certainly are outdated (except for a few).
>>> http://cdd.alioth.debian.org/science/tasks/statistics.html
>>>
>>> is not a proper place for any R related package?
>>
>> Hm. No, you are right, all the debian-med R bits could move right there.
>
> So I'll go on moving my R stuff to debian-science ...
Save your time, I'd say. The debian/control file indicates where to find the source. And
at least r-cran-qtl is not too wrongly found under the hood of Debian-Med.
>> It is a non-issue. Someone wasting an hour here or there on something
>> that has already
>> been done is not too bad. Probably more ideas arise when comparing the
>> efforts for a later
>> merger.
>
> I do not think that the comparison with a formerly done non functional
> package will be done by anybody if there is a working package. I
> repeat: I care about the time you might waste. You are an
> important brick in our Debian Med building and would try to
> make you as strong as possible which is not the case if you
> spend your time on stuff which is simply removed later on.
We had a case _within_ Debian-Med when Charles did not find libbioperl-runtime and started
an effort on his own for bioperl-runtime. You cannot avoid such things. And it has little
to do with the Blend or Alioth project one is in.
>> I am very emotionless in this issue.
>
> Good to hear this! Same on my side (even if it might seem differently).
You have some good points in what you are saying. The integration of pkg-escience with
some blend certainly helps visibility, particularly since debian-med.alioth.debian.org is
up. However, the current situation lets single developers join many alioth projects, and
the contributor to a single package has the rights to edit many. I don't like that since
changes (intentionally or not) may not be noticed. pkg-scicomp and pkg-java are basically
too large to check out as a whole. And Debian-Med develops towards such a complexity, too.
An "all in one" or "poly in oligo" will not scale for long, at least not if we are
successful. We should start thinking about what is coming next.
Many greetings
Steffen
Reply to: