1 |
On Tue, 2007-10-16 at 06:57 -0700, M. Edward (Ed) Borasky wrote: |
2 |
|
3 |
> 1. I'm not sure the idea of integrating, say, R packages, into Portage |
4 |
> is a good one. Debian has a lot of R packages in their repository, but |
5 |
> that's mainly because one developer, Dirk Eddelbuettel, took that on as |
6 |
> a personal mission. For that matter, I don't know that Portage really |
7 |
> *needs* to have "tight" integration with any other package management |
8 |
> systems. In other words, does a CPAN Perl package really need to be |
9 |
> wrapped in an ebuild, or could a Gentoo user just as easily install CPAN |
10 |
> packages directly? The same goes for Ruby gems -- it's only marginally |
11 |
> more convenient for a Rubyist to have gems in Portage, and you'll never |
12 |
> have them *all. If you have the developer resources, sure, why not, but |
13 |
> aren't there better things the developers could be doing? In any event, |
14 |
> I use R and its packages heavily and don't see the need to "emerge |
15 |
> Rcmdr" -- R's native package management system is fine. So is Ruby's |
16 |
> "rubygems" package management system. |
17 |
|
18 |
Not saying 100 R packages => 100 ebuilds, but passing proper flags, |
19 |
building deps and all could be wrapped in a nice gentoo way (btw, is |
20 |
paludis doing this?). Anyway this was just a project idea in a todo list |
21 |
and should go to another thread, or the corresponding bug. |
22 |
|
23 |
> 2. Don't be afraid to kick something out of the distro if nobody wants |
24 |
> to maintain it. It's no big deal to install a package from upstream |
25 |
> source. As far as I'm concerned, in most cases the only difference is |
26 |
> that it ends up in /usr/local instead of in /usr and I have to manually |
27 |
> load the dependencies. |
28 |
|
29 |
This is also an area where we could use some help. Do you feel any |
30 |
packages are unmaintained or could be removed? If yes, file a bug, say |
31 |
your word on the wiki, ... |
32 |
|
33 |
-- |
34 |
Sébastien |