1 |
> So, fellow devs, what's new with development? For those interested, genlop |
2 |
> has |
3 |
> migrated into gentoo as a project with the permission of upstream, which |
4 |
> no |
5 |
> longer maintain it. Um...any new tools or projects people are working on? |
6 |
> |
7 |
> Anyone? |
8 |
|
9 |
My current projects include: |
10 |
|
11 |
block_sync glep: really..I'm still working on it..it's almost done, this will |
12 |
enable developers to block the cvs->rsync sync to repair major tree |
13 |
damage. hopefully end of the month for this. |
14 |
|
15 |
Project Leads Glep: This is a new idea, mostly making tiny bits of work |
16 |
for project leads so we can get an idea of what is going on within Gentoo. |
17 |
Still in the 'soliciting initial feedback' phase. I'm also working on |
18 |
the app needed to support this idea (writing it in ruby for now). |
19 |
|
20 |
LDAP Improvements: Slowly working on learning ruby-activeLDAP and using it |
21 |
to punt perl_ldap because I think perl_ldap sucks. Once the newer shinier |
22 |
app is written I plan on writing up some training for it. This is for the |
23 |
overall move of data into ldap which is then used to generate things like |
24 |
userinfo.xml and other web-based data. One place for updates folks.. |
25 |
|
26 |
Gentoolkit: I just ported the new portage namespace to these tools and |
27 |
fixed a few bugs. Sadly I also wrote a broken patch to echangelog that |
28 |
got the newest rev of gentoolkit masked. Fixing echangelog is on my list |
29 |
of things to do. If you are better than me at perl (probably true for |
30 |
many of you) I could use some help here ;) |
31 |
|
32 |
Portage Unit Tests and /etc/portage: |
33 |
These are on the backburner for now but there are nice OO based classes |
34 |
for /etc/portage config files; this means if you were so inclined you |
35 |
could store that data in a db and write classes to read from the db |
36 |
instead of from files. This functionality is not yet enabled in trunk as |
37 |
I have no idea how to bolt it on to portage.config yet; but I'm working on |
38 |
it. |
39 |
|
40 |
The /etc/portage config rewrite is to enable me to test large classes like |
41 |
portage.config that read from tons of files (reading from files is |
42 |
generally a cardinal sin in unit testing). |
43 |
|
44 |
The testing of course is to enable the portage team to make changes and |
45 |
not break stuff. Most of the new features I've been working on are driven |
46 |
using Test Driven Development (TDD) and involve gutting old n busted |
47 |
functions; replacing with new ones. Still need more tests though. |
48 |
|
49 |
Ugh, and I thought I was trying to do less... |
50 |
|
51 |
Oh Summer of Code...reviewed nearly all of the apps. Voting is on Sunday? |
52 |
|
53 |
-Alec |
54 |
|
55 |
-- |
56 |
gentoo-dev@g.o mailing list |