1 |
Alex Tsui wrote: |
2 |
> There is a set of octave-forge-* ebuilds in the science overlay can be |
3 |
> consolidated and managed by the paludis package manager. Paludis works |
4 |
> internally with repositories, so I want to implement an octave-forge |
5 |
> repository that will sync and un/install octave-forge packages. All of |
6 |
> octave-forge's packages are organized into four repositories, |
7 |
> basically folders. Also, dependency information is included in each |
8 |
> octave-forge package in a standard description file. This is |
9 |
> everything needed to write a syncer in paludis, and then we can take |
10 |
> advantage of paludis to do dependency resolution based on the |
11 |
> descriptions, saving a whole tree of ebuilds to maintain. |
12 |
> |
13 |
> Most octave-forge packages depend on themselves or other octave-forge |
14 |
> packages, but some call for external packages. I haven't used paludis |
15 |
> yet, but I guess since it can be configured to do the work of portage, |
16 |
> portage is just another repository under paludis and so this type of |
17 |
> dependency can also be resolved, too. |
18 |
> |
19 |
|
20 |
paludis seems to have a codebase that should allow to implement a lot of |
21 |
these g-* projects, so why not. For octave I don't think there is an |
22 |
easy repository to sync as you might do with portage or R. You might |
23 |
have to make a way to create a special sync from the web page or |
24 |
maintain a local index/database. Also as you noted there are packages |
25 |
with external deps. There aren't that many for now, so either make them |
26 |
as standard ebuilds, or find a way for packages to talk cross repositories. |
27 |
|
28 |
-- |
29 |
Sébastien |