1 |
Hi Sebastien, |
2 |
|
3 |
Please forgive me for my lack of knowledge about package managers, but |
4 |
what systems are in place to generate ebuilds on the fly? And is there |
5 |
any compatibility between the different package managers in that |
6 |
sense? Would it be possible to make an overlay build a repository of R |
7 |
packages on the fly? If ebuilds are generated on the fly, how will we |
8 |
deal with nontrivial ebuilds? |
9 |
|
10 |
As always, there are a number of advantages to make the package |
11 |
manager do the hard work. I guess some more benefits would, among |
12 |
many, be: emerge world updates R packages too (ie. centralized |
13 |
updating), packages in portage can pull in R packages without user |
14 |
interference, and users can relatively easily install R packages with |
15 |
patches. |
16 |
|
17 |
Thanks, |
18 |
Auke. |
19 |
|
20 |
2010/3/19 Sébastien Fabbro <bicatali@g.o>: |
21 |
> On Thursday 18 March, Auke Booij wrote: |
22 |
> |
23 |
>> 1. R package installer (also see gentoo-wiki.com). R has a lot of |
24 |
>> additional packages, so it is not feasible to manually create and |
25 |
>> maintain ebuilds for all of them. There are a number of databases |
26 |
>> containing these additional packages, including CRAN and Bioconductor. |
27 |
>> Three reasonable solutions are: 1. create a big ebuild with loads and |
28 |
>> loads of USE flags which compiles and installs the wanted R packages |
29 |
>> as one big package (not the best, since this is exactly what we want |
30 |
>> to avoid with Gentoo, and we would indeed need loads of use flags), 2. |
31 |
>> generate ebuilds for all packages (this would need regular running of |
32 |
>> scripts, and would probably need for its own overlay), 3. install to |
33 |
>> the filesystem without letting the package manager know about anything |
34 |
>> (ehm... I guess this is not a reasonable solution, after all). Are |
35 |
>> there any ideas about how to solve this, and how R usually installs |
36 |
>> them? Sebastien fabbro, I cc'd you, are you still interested in |
37 |
>> mentoring this? |
38 |
> |
39 |
> Hi, |
40 |
> |
41 |
> CRAN/Bioconductor support in Gentoo is definitely something worth |
42 |
> exploring and has been requested by several Gentoo users. |
43 |
> Solutions 1. and 3. are not something I would pursue. With the |
44 |
> thousands R packages to deal with, you would want either on-the-fly |
45 |
> ebuild generation or the package manager to directly deal with the CRAN |
46 |
> format (which is I think what the paludis folks started doing until CRAN |
47 |
> changed its format again). Any solution leading to complex handling, |
48 |
> the users will return to the R CMD INSTALL quickly. |
49 |
> Keep in mind that one of the main reason not to use the R default |
50 |
> package management system but a Gentoo one is to get R-external |
51 |
> dependencies from the portage tree. |
52 |
> |
53 |
> I am not sure I will find time to mentor the full Summer. If anyone |
54 |
> applying for this project makes a good application, I'll push this to |
55 |
> my fellow devs to give a hand in the mentoring process. |
56 |
> |
57 |
> -- |
58 |
> Sebastien |
59 |
> |
60 |
> |