1 |
Hi everyone. The gentoo-guis mail list is active, apparently never was |
2 |
de-activated. But is now listed on the mail list page along with the |
3 |
only gentoo link to the gentoo-guis project page. |
4 |
|
5 |
There are several things we need to get to Andrew <galiven> so that he |
6 |
can properly update the page with all our projects. |
7 |
|
8 |
1) project name, developer(s), status, homepage link, brief description |
9 |
blurb... |
10 |
2) your publishable info Name, email, blog maybe. |
11 |
3) if your not already signed up for the gentoo-guis email list, please |
12 |
do. |
13 |
|
14 |
Araujo, we need you to submit the ventoo info as well. |
15 |
|
16 |
lxnay, I don't know if you want packagekit listed here as well. Since |
17 |
it is not gentoo specific, I don't know if it qualifies. Araujo will |
18 |
need to answer that. |
19 |
|
20 |
I'm cc'ing several people here, so sorry if you get double copies. I |
21 |
want to make sure they know about the list. |
22 |
|
23 |
Araujo, We need you to get in touch with dberkholz about getting the |
24 |
gentoo-guis project page linked in somewhere. I was talking with him on |
25 |
irc about it. Please find a little time to arrange that. :) |
26 |
Also please arrange for galiven to be able to submit the updated page |
27 |
for testing and final updating. Not being a gentoo developer limits my |
28 |
ability to get some things done. I have been in contact with dabbot |
29 |
about the page update. He had said he would run it through guide.xml for |
30 |
testing/previewing when we were ready. |
31 |
|
32 |
I know Andrew started a new job this week, so won't have as much time |
33 |
just yet. He still has to make a good impression ;) |
34 |
|
35 |
On other news, gtk-3 is about to hit the tree, so several of us will |
36 |
have porting work to do as well. |
37 |
|
38 |
So, here's hoping we can generate more interest and help in getting all |
39 |
out projects moving forward. |
40 |
|
41 |
Some late breaking news... I've been adding/improving more to layman's |
42 |
api recently, discovering shortcomings, etc.. Partially due to starting |
43 |
a pothole plug-in, partially for starting portage's integration of the |
44 |
new layman api. For those that want to check it out. So far I have the |
45 |
git repo posted at |
46 |
|
47 |
http://dev.gentooexperimental.org/~dol-sen/git/portage.git/ |
48 |
|
49 |
the layman_sync branch. |
50 |
|
51 |
New, but not yet committed and pushed to the above link. |
52 |
I've added a new OptionConfig class which subclasses BareConfig and |
53 |
makes it easier to set up the options to your liking. I've also removed |
54 |
some of the xml requirement in the backends which made it possible to |
55 |
now add repo's dynamically via a python dictionary containing the needed |
56 |
info, rather than creating & parsing an xml file. I've also added an |
57 |
utils function for creating it with the correct keys. This has opened |
58 |
up more possibilities for using layman. One of the tests I did was in a |
59 |
live python console session . I created an empty Db, added a fake test |
60 |
repo, added my working gentoolkit git clone and and then activated it to |
61 |
sync it which it happily did successfully. Once I finish that I'll |
62 |
commit them an let you know again. |
63 |
|
64 |
I am also contemplating extending the repo attributes to be able to |
65 |
store more of it's info such as it's install location so that you can |
66 |
have them located anywhere in the file system. More on that another |
67 |
time. |
68 |
|
69 |
Bye for now |
70 |
-- |
71 |
Brian Dolbec <brian.dolbec@×××××.com> |