From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] RFE: adding optional freshmeat id to metadata.xml
Date: Sun, 14 Dec 2003 16:43:12 +0100 [thread overview]
Message-ID: <200312141643.24914.pauldv@gentoo.org> (raw)
In-Reply-To: <3FD6BEEB.2070408@gentoo.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1241 bytes --]
On Wednesday 10 December 2003 07:36, Sandy McArthur wrote:
> If this is the wrong place let me know.
>
> How about adding an optional freshmeat tag to the metadata.xml that
> could be used to robustly link the package with the contents of
> http://freshmeat.net/backend/ fm-projects.rdf (warning 72 meg file).
> This could be used to enable http://packages.gentoo.org/ to be updated
> with information on which packages had newer upstream releases since
> package maintainers frequently announce releases with freshmeat. A link
> to the freshmeat package page could be added which some users may find a
> useful resource. Freshmeat tracks a lot of useful metadata that
> package.gentoo.org can take advantage of like 'Development Status' which
> is from 'alpha' to 'mature' and indicates what level of maturity the
> package author thinks of her own work. Umm, links to screen shots or
> demo sites, dependency information, the more I think about it the
> possibly useful information that could be collected for free.
What would be needed for such a tag? (Except that dev's need to use it for it
to be usefull)
Paul
--
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-14 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 6:36 [gentoo-portage-dev] RFE: adding optional freshmeat id to metadata.xml Sandy McArthur
2003-12-14 15:43 ` Paul de Vrieze [this message]
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=200312141643.24914.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-portage-dev@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