Re: [gentoo-soc] Looking for a mentor for a Portage SOC Project

[Colleen Josephson <cjoseph@mit.edu>]

[-- Attachment #1: Type: text/plain, Size: 4107 bytes --]

Thanks Jeremy,

I suppose part of the timeline is me figuring out the inner workings of
Portage and how to work with the existing code,
Do you have any ideas for expansions that would be more significant? Also,
any comments on the timelines for the rest of the ideas?

Perhaps I could merge the work with Portage into the ebuild generator
project--I have often wished for the ability to take source I have
downloaded and easily work it into a local Portage layover.

Perhaps half the summer on Portage features and half on the e-build
generator would be more reasonable?


On Wed, Mar 30, 2011 at 3:57 PM, Jeremy Olexa <darkside@gentoo.org> wrote:

> On Wed, 30 Mar 2011 15:22:47 -0500, Colleen Josephson wrote:
>
>> Im interested in expanding the Portage "tags" idea listed on the wiki.
>> To make it SOC-worthy, it obviously needs to be expanded.
>>
>> I have thought of a few possibilities:
>> -Integrate eix into Portage as a replacement to search
>>  -Add a Debian-apt style autocomplete
>> -Add a flag to force the removal of config files when removing a
>> package, if desired
>> -Add a feature that lists which commands were installed after merging
>> a package
>> e.g. after installing net-tools successfully, emerge would say:
>>  "Commands in net-tools: arp, hostname, ifconfig, ipmaddr, iptunnel,
>> mii-tool, nameif, netstat, plipconfig, rarp, route and slattach"
>> For packages that install something in /etc/init.d, it would list how
>> to start it: e.g. "To start service, run /etc/init.d/servicename
>> start"
>>  It would also be nice to have the ability to look this up to see the
>> commands associated with an already installed package:
>> e.g. "emerge --list-commands packagename" or something similar.
>>
>> I am trying to determine whether or not these features are enough to
>> fill a summer, or if I need more.
>>  There are 14 weeks in SOC, 13 weeks of coding if I leave the last
>> week for polishing things.
>> Im thinking: 3 weeks for eix integration, 1-2 weeks for tags, 1 week
>> for the --remove-config flag, 2-3 weeks for the autocomplete, and 4
>> weeks for the "commands installed" feature.
>>  It looks like I need 1 more "agenda item" to fill the summer. Any
>> suggestions?
>>
>
> Hello, thanks for your interest in GSOC. I don't want to shoot you down
> right away, but I think you are seriously over estimating the amount of time
> needed and you'll find this proposal to be too easy. For example, I just did
> you "4 weeks" of "commands installed feature" in 30 seconds. :)
>
> % cat /etc/portage/bashrc
> if [[ $EBUILD_PHASE == postinst ]]; then
>        ewarn "BINARIES: "
>        ewarn $(qlist ${PN} | grep bin)
> fi
>
> % sudo emerge -av1 less
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [binary   R   ] sys-apps/less-436  USE="unicode"
>
> Total: 1 package (1 reinstall, 1 binary), Size of downloads: 0 kB
>
> Would you like to merge these packages? [Yes/No]
>
>> Emerging binary (1 of 1) sys-apps/less-436
>>>> Installing (1 of 1) sys-apps/less-436
>>>> Jobs: 1 of 1 complete                           Load avg: 0.34, 0.46,
>>>> 0.64
>>>>
>>>
>  * Messages for package sys-apps/less-436:
>
>  * BINARIES:
>  * /usr/bin/code2color /usr/bin/lesspipe /usr/bin/lessecho
> /usr/bin/lesspipe.sh /usr/bin/lesskey /usr/bin/less
>
>> Auto-cleaning packages...
>>>>
>>>
>  No outdated packages were found on your system.
>>>>
>>>
>  * GNU info directory index is up-to-date.
>
> Granted, that is in bash, but still. On that note, feel free to expand your
> ideas. :)
> -Jeremy
>
>
>
>> Do these timeframes sound reasonable? I have 3-4 years of coding
>> experience, with 2 years of Python.
>>
>> Im in need of a mentor ASAP so I can get feedback while writing up my
>> proposal, and have somebody point me to a good bugfix to do.
>>
>> --
>> Colleen Josephson
>> Dept. of Electrical Engineering and Computer Science
>> Massachusetts Institute of Technology
>> Class of 2013
>>
>
>
>


-- 
Colleen Josephson
Dept. of Electrical Engineering and Computer Science
Massachusetts Institute of Technology
Class of 2013

[-- Attachment #2: Type: text/html, Size: 6405 bytes --]