1 |
El 24/ago/2005 a las 04:01 -0300, Jonas me decía: |
2 |
> >Second, the whole idea is to do this for non-connected systems. Meaning, a |
3 |
> >solution not involving the Internet... =) |
4 |
> If you're refering to the fact that the person doesn't have an internet |
5 |
> connection when he wants to view this information throught the emerge |
6 |
> interface, then you're wrong. When you want to install or you're just |
7 |
> searching for a package you're using the emerge interface , when you |
8 |
> need more info you have to 1) open your browser 2) type in the url (if |
9 |
> you're lucky you know the url or it's in your browsers cache) 3) search |
10 |
> for the package on the website , while instead you could just do |
11 |
> something like emerge --desc package. Now what's quicker and makes more |
12 |
> sence ? |
13 |
|
14 |
Exactly! That's what i'm refering to. It's not an issues of connection it's an |
15 |
issue of lazyness! It's like: "-- hey what are you doing this weekend? -- don't |
16 |
know, it's cold and raining, i think i'm gonna sit in my throne and check what's |
17 |
new on 'app-vim' to improve my vimyness, if find something interesting i'll |
18 |
check the package webpage." |
19 |
|
20 |
For now i'm using 'questo': |
21 |
=== script ==== |
22 |
#!/bin/bash |
23 |
# lun may 2 20:57:24 ART 2005 |
24 |
# conan - GPLed |
25 |
# |
26 |
# script to check for apps on rainy sunday morning |
27 |
|
28 |
BASE_DIR="/usr/portage/" |
29 |
|
30 |
[ $# -ne 1 ] && echo "Uso: questo <category>" && exit 0 |
31 |
|
32 |
cd $BASE_DIR$1 |
33 |
for package in * ; do |
34 |
eix "^$paquete\$" |
35 |
echo "Looking for: $1/$paquete. ENTER to continue..." |
36 |
read |
37 |
done |
38 |
=== end script ==== |
39 |
|
40 |
Now i took sugestion from Ciaran to look in metadata.xml, i check a couple by |
41 |
hand and see the 'longdesc' field but... with short descriptions! Now maybe i |
42 |
just choose two with bad luck, but i got a feeling that gentoo maintainers |
43 |
doesn't like to provide longdesc, although there is the posibility. |
44 |
|
45 |
I was thinking of doing a little script that gives longdesc found in metadata to |
46 |
confirm this, but since i don't know nothing about xml, think it gonna take a |
47 |
little bit more that if there were already an application to check 'metadata.xml' |
48 |
fields. 'emerge', 'equery' and 'eix' wich are the administration tools i use |
49 |
everyday don't say nothing about this, i think all of them use de description |
50 |
field in ebuilds. I wonder if somebody knows another app to do this? |
51 |
|
52 |
If not, the idea of the script is more less this: |
53 |
lslongdesc package|category|all |
54 |
|
55 |
where: |
56 |
- 'package' gives longdesc of package |
57 |
- 'category' gives longdesc of all packages in category |
58 |
- and 'all' gives them all flooding your screen with info you never gonna eat... |
59 |
but that is there. |
60 |
|
61 |
It's so simple that i'm sure there must be an app (or compound of them) that |
62 |
already do this. |
63 |
|
64 |
-- |
65 |
Fernando Canizo - http://www.lugmen.org.ar/~conan/ |
66 |
Olmstead's Law: |
67 |
After all is said and done, a hell of a lot more is said than done. |
68 |
-- |
69 |
gentoo-user@g.o mailing list |