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