1 |
Thanks Jeremy, |
2 |
|
3 |
I suppose part of the timeline is me figuring out the inner workings of |
4 |
Portage and how to work with the existing code, |
5 |
Do you have any ideas for expansions that would be more significant? Also, |
6 |
any comments on the timelines for the rest of the ideas? |
7 |
|
8 |
Perhaps I could merge the work with Portage into the ebuild generator |
9 |
project--I have often wished for the ability to take source I have |
10 |
downloaded and easily work it into a local Portage layover. |
11 |
|
12 |
Perhaps half the summer on Portage features and half on the e-build |
13 |
generator would be more reasonable? |
14 |
|
15 |
|
16 |
On Wed, Mar 30, 2011 at 3:57 PM, Jeremy Olexa <darkside@g.o> wrote: |
17 |
|
18 |
> On Wed, 30 Mar 2011 15:22:47 -0500, Colleen Josephson wrote: |
19 |
> |
20 |
>> Im interested in expanding the Portage "tags" idea listed on the wiki. |
21 |
>> To make it SOC-worthy, it obviously needs to be expanded. |
22 |
>> |
23 |
>> I have thought of a few possibilities: |
24 |
>> -Integrate eix into Portage as a replacement to search |
25 |
>> -Add a Debian-apt style autocomplete |
26 |
>> -Add a flag to force the removal of config files when removing a |
27 |
>> package, if desired |
28 |
>> -Add a feature that lists which commands were installed after merging |
29 |
>> a package |
30 |
>> e.g. after installing net-tools successfully, emerge would say: |
31 |
>> "Commands in net-tools: arp, hostname, ifconfig, ipmaddr, iptunnel, |
32 |
>> mii-tool, nameif, netstat, plipconfig, rarp, route and slattach" |
33 |
>> For packages that install something in /etc/init.d, it would list how |
34 |
>> to start it: e.g. "To start service, run /etc/init.d/servicename |
35 |
>> start" |
36 |
>> It would also be nice to have the ability to look this up to see the |
37 |
>> commands associated with an already installed package: |
38 |
>> e.g. "emerge --list-commands packagename" or something similar. |
39 |
>> |
40 |
>> I am trying to determine whether or not these features are enough to |
41 |
>> fill a summer, or if I need more. |
42 |
>> There are 14 weeks in SOC, 13 weeks of coding if I leave the last |
43 |
>> week for polishing things. |
44 |
>> Im thinking: 3 weeks for eix integration, 1-2 weeks for tags, 1 week |
45 |
>> for the --remove-config flag, 2-3 weeks for the autocomplete, and 4 |
46 |
>> weeks for the "commands installed" feature. |
47 |
>> It looks like I need 1 more "agenda item" to fill the summer. Any |
48 |
>> suggestions? |
49 |
>> |
50 |
> |
51 |
> Hello, thanks for your interest in GSOC. I don't want to shoot you down |
52 |
> right away, but I think you are seriously over estimating the amount of time |
53 |
> needed and you'll find this proposal to be too easy. For example, I just did |
54 |
> you "4 weeks" of "commands installed feature" in 30 seconds. :) |
55 |
> |
56 |
> % cat /etc/portage/bashrc |
57 |
> if [[ $EBUILD_PHASE == postinst ]]; then |
58 |
> ewarn "BINARIES: " |
59 |
> ewarn $(qlist ${PN} | grep bin) |
60 |
> fi |
61 |
> |
62 |
> % sudo emerge -av1 less |
63 |
> |
64 |
> These are the packages that would be merged, in order: |
65 |
> |
66 |
> Calculating dependencies... done! |
67 |
> [binary R ] sys-apps/less-436 USE="unicode" |
68 |
> |
69 |
> Total: 1 package (1 reinstall, 1 binary), Size of downloads: 0 kB |
70 |
> |
71 |
> Would you like to merge these packages? [Yes/No] |
72 |
> |
73 |
>> Emerging binary (1 of 1) sys-apps/less-436 |
74 |
>>>> Installing (1 of 1) sys-apps/less-436 |
75 |
>>>> Jobs: 1 of 1 complete Load avg: 0.34, 0.46, |
76 |
>>>> 0.64 |
77 |
>>>> |
78 |
>>> |
79 |
> * Messages for package sys-apps/less-436: |
80 |
> |
81 |
> * BINARIES: |
82 |
> * /usr/bin/code2color /usr/bin/lesspipe /usr/bin/lessecho |
83 |
> /usr/bin/lesspipe.sh /usr/bin/lesskey /usr/bin/less |
84 |
> |
85 |
>> Auto-cleaning packages... |
86 |
>>>> |
87 |
>>> |
88 |
> No outdated packages were found on your system. |
89 |
>>>> |
90 |
>>> |
91 |
> * GNU info directory index is up-to-date. |
92 |
> |
93 |
> Granted, that is in bash, but still. On that note, feel free to expand your |
94 |
> ideas. :) |
95 |
> -Jeremy |
96 |
> |
97 |
> |
98 |
> |
99 |
>> Do these timeframes sound reasonable? I have 3-4 years of coding |
100 |
>> experience, with 2 years of Python. |
101 |
>> |
102 |
>> Im in need of a mentor ASAP so I can get feedback while writing up my |
103 |
>> proposal, and have somebody point me to a good bugfix to do. |
104 |
>> |
105 |
>> -- |
106 |
>> Colleen Josephson |
107 |
>> Dept. of Electrical Engineering and Computer Science |
108 |
>> Massachusetts Institute of Technology |
109 |
>> Class of 2013 |
110 |
>> |
111 |
> |
112 |
> |
113 |
> |
114 |
|
115 |
|
116 |
-- |
117 |
Colleen Josephson |
118 |
Dept. of Electrical Engineering and Computer Science |
119 |
Massachusetts Institute of Technology |
120 |
Class of 2013 |