public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Crute <mcrute@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why gentoo doesn't have long description?
Date: Wed, 24 Aug 2005 10:03:59 -0400	[thread overview]
Message-ID: <558b73fb050824070378013489@mail.gmail.com> (raw)
In-Reply-To: <20050824110803.GA4532@lugmen.org.ar>

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

First of all, sorry about top posting that's the way Gmail does it and you 
cant change the settings. 

Also if you are looking for a lazy man's way of getting a package 
description try `emerge -s packagename` and it prints out a lot of 
information as well as a short description of the package. I have never seen 
a long description such as those used to build Debian packages anywhere in 
portage and don't really think it would be useful anyhow. So try emerge -s 
and if you need more info go to the packae's website. That would be my 
advice. Oh, and emerge -s works off the metadata so you dint need an 
Internet connection.

-Mike. 

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


-- 
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation

Linux, because reboots are for installing hardware.
"In a world without walls and fences, who needs windows and gates?"

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

  reply	other threads:[~2005-08-24 14:12 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 11:26 [gentoo-user] why gentoo doesn't have long description? conan
2005-08-23 15:45 ` Jonas Geiregat
2005-08-23 21:47 ` Ciaran McCreesh
2005-08-24  3:39   ` Michael Crute
2005-08-24  6:48     ` Matan Peled
2005-08-24  7:01       ` Jonas Geiregat
2005-08-24 11:08         ` Fernando Canizo
2005-08-24 14:03           ` Michael Crute [this message]
2005-08-24 14:24             ` David Morgan
2005-08-24 14:39               ` Michael Crute
2005-08-24 14:49                 ` David Morgan
2005-08-24 14:57               ` Daniel da Veiga
2005-08-24 15:08                 ` [gentoo-user] very OT (was: why gentoo doesn't have long description?) Christoph Gysin
2005-08-24 15:13                 ` [gentoo-user] why gentoo doesn't have long description? David Morgan
2005-08-24 15:19                 ` Ciaran McCreesh
2005-08-24 17:14                   ` Michael Crute
2005-08-24 17:33                     ` Matan Peled
2005-08-24 18:00                       ` Michael Crute
2005-08-24 20:33                   ` Jonathan Nichols
2005-08-24 20:52                     ` Holly Bostick
2005-08-24 22:40                       ` Jonathan Nichols
2005-08-24 21:14                     ` Anthony E. Caudel
2005-08-24 21:22                       ` Volker Armin Hemmann
2005-08-24 21:24                       ` Dave Nebinger
2005-08-24 21:25                       ` Ciaran McCreesh
2005-08-24 21:45                       ` Jerry McBride
2005-08-24 21:54                         ` David Morgan
2005-08-24 22:43                         ` Jonathan Nichols
2005-08-25 15:42                           ` A. Khattri
2005-08-25 16:49                             ` Michael Crute
2005-08-26  2:05                             ` W.Kenworthy
2005-08-26  7:36                               ` Marco Matthies
2005-08-26 14:17                                 ` A. Khattri
2005-08-24 23:01                         ` Anthony E. Caudel
2005-08-25  0:11                           ` Matt Nordhoff
2005-08-25 15:39                         ` A. Khattri
2005-08-25 21:52                           ` Neil Bothwick
2005-08-26 14:36                             ` Billy Holmes
2005-08-26 15:06                               ` Daniel da Veiga
2005-08-26 15:21                                 ` Holly Bostick
2005-08-26 15:40                                   ` Martin Marcher
2005-08-26 17:10                                 ` Neil Bothwick
2005-08-26 18:29                                 ` A. Khattri
2005-08-24 15:03             ` Jonas Geiregat
2005-08-24 15:01           ` Jonas Geiregat
2005-08-24 20:23           ` [gentoo-user] " Moshe Kaminsky
2005-08-25 23:57 ` [gentoo-user] " Holly Bostick
2005-08-26  0:19   ` Nick Rout
2005-08-26 13:12   ` Fernando Canizo
2005-08-29 20:02     ` Jonas Geiregat
2005-08-29 19:31       ` Holly Bostick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=558b73fb050824070378013489@mail.gmail.com \
    --to=mcrute@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox