From: "Sébastien Fabbro" <bicatali@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 16:03:23 +0100 [thread overview]
Message-ID: <1192547003.5412.138.camel@zeca> (raw)
In-Reply-To: <4714C33E.8060400@cesmail.net>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On Tue, 2007-10-16 at 06:57 -0700, M. Edward (Ed) Borasky wrote:
> 1. I'm not sure the idea of integrating, say, R packages, into Portage
> is a good one. Debian has a lot of R packages in their repository, but
> that's mainly because one developer, Dirk Eddelbuettel, took that on as
> a personal mission. For that matter, I don't know that Portage really
> *needs* to have "tight" integration with any other package management
> systems. In other words, does a CPAN Perl package really need to be
> wrapped in an ebuild, or could a Gentoo user just as easily install CPAN
> packages directly? The same goes for Ruby gems -- it's only marginally
> more convenient for a Rubyist to have gems in Portage, and you'll never
> have them *all. If you have the developer resources, sure, why not, but
> aren't there better things the developers could be doing? In any event,
> I use R and its packages heavily and don't see the need to "emerge
> Rcmdr" -- R's native package management system is fine. So is Ruby's
> "rubygems" package management system.
Not saying 100 R packages => 100 ebuilds, but passing proper flags,
building deps and all could be wrapped in a nice gentoo way (btw, is
paludis doing this?). Anyway this was just a project idea in a todo list
and should go to another thread, or the corresponding bug.
> 2. Don't be afraid to kick something out of the distro if nobody wants
> to maintain it. It's no big deal to install a package from upstream
> source. As far as I'm concerned, in most cases the only difference is
> that it ends up in /usr/local instead of in /usr and I have to manually
> load the dependencies.
This is also an area where we could use some help. Do you feel any
packages are unmaintained or could be removed? If yes, file a bug, say
your word on the wiki, ...
--
Sébastien
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-16 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:39 [gentoo-science] sci team help Sébastien Fabbro
2007-10-15 19:09 ` C Y
2007-10-15 19:11 ` Yuriy Rusinov
2007-10-15 20:26 ` Sébastien Fabbro
2007-10-23 15:16 ` Redouane Boumghar
2007-10-15 20:14 ` Donnie Berkholz
2007-10-15 21:02 ` Jukka Ruohonen
2007-10-16 1:19 ` Markus Luisser
2007-10-16 9:50 ` Sébastien Fabbro
2007-10-16 10:18 ` Sébastien Fabbro
2007-10-16 5:01 ` Andrey G. Grozin
2007-10-16 7:20 ` Donnie Berkholz
2007-10-16 9:54 ` Sébastien Fabbro
2007-10-16 10:04 ` Jukka Ruohonen
2007-10-16 10:15 ` Donnie Berkholz
2007-10-16 2:41 ` Nuno Sucena Almeida
2007-10-16 13:57 ` M. Edward (Ed) Borasky
2007-10-16 15:03 ` Sébastien Fabbro [this message]
2007-10-16 19:11 ` Nuno Sucena Almeida
2007-10-16 22:51 ` Donnie Berkholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1192547003.5412.138.camel@zeca \
--to=bicatali@gentoo.org \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox