1 |
Hello, |
2 |
So far the progress has been quite smooth. Syncing from the main PEAR |
3 |
repository/channel works, dare I say, perfectly, and from tests it |
4 |
seems that alternative channels are synced to without problems, too. |
5 |
Thanks to PEAR channels being based upon XML and its good |
6 |
documentation, I've not encountered the problems tulcod (hi!) had with |
7 |
parsing CRAN files. |
8 |
Two things are left on my agenda for now, dependency support and installing. |
9 |
Installing won't be too hard, the package.xml file is pretty simple. |
10 |
The only problem here is that PEAR only provides with md5sums of each |
11 |
separate file inside the package, but not of the whole package (at |
12 |
least that's what it seems like). Also, I'm not sure if md5sums are |
13 |
enough, since the packages seem to be validated with other hash |
14 |
functions. |
15 |
Dependency support is a fairly delicate matter. There exist two |
16 |
versions of package.xml, the old 1.0 and the new 2.0. While the |
17 |
differences between them are fairly small, the biggest issue is the |
18 |
completely re-designed, incompatible dependency support in version |
19 |
2.0. Since almost all PEAR packages today use version 2.0, and the |
20 |
ones still on 1.0 seem to be mostly unmaintained packages and old |
21 |
versions, I might just as well drop support for 1.0 altogether - this |
22 |
will definitely simplify the code (and if nobody will ever use the 1.0 |
23 |
codepaths, then what's the point...). For now I will only support 2.0, |
24 |
if there is substantial demand I will consider 1.0 in the future (if |
25 |
time permits, then during GSOC, if not, then afterwards). |
26 |
The developers of g-* (iElectric, tulcod and me) will be meeting on |
27 |
IRC on Monday, 28 June to discuss progress and g-common. This is the |
28 |
next step - now that we know our requirements, we can sit down to |
29 |
g-common properly and come up with a good solution. Of course the g-* |
30 |
tools/drivers won't be 100% ready by then, however, we'll know where |
31 |
we're standing in terms of unification - and will be able to further |
32 |
develop our drivers in a more co-ordinated way. |
33 |
By the big meeting, I hope to have the installer and the dependencies ready. |
34 |
Also, I'll try to get a git repo so that everyone can watch me coding. |
35 |
I'm on IRC (wiktor_b #gentoo-soc) most of the time, however, I'll be |
36 |
away from this Tuesday (the 22nd), and won't be online very often, |
37 |
until the end of the month, I'll still be doing some coding all the |
38 |
time though. |
39 |
Happy coding/mentoring all! |
40 |
~wiktor. |