public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: New irc data field in layman's repositories.xml file format
Date: Tue, 13 Mar 2012 01:33:28 -0700	[thread overview]
Message-ID: <1331627608.29064.88.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <robbat2-20120312T084928-929919204Z@orbis-terrarum.net>

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

On Mon, 2012-03-12 at 08:49 +0000, Robin H. Johnson wrote:
> On Mon, Mar 12, 2012 at 08:52:20PM +1300, Kent Fredric wrote:
> > On 11 March 2012 22:09, Brian Dolbec <dolsen@gentoo.org> wrote:
> > >
> > > eg:
> > >
> > >     <irc>Channel #gentoo-guis on the freenode network</irc>
> > > or
> > >     <irc>#gentoo-guis on the freenode IRC network, irc://irc.gentoo.org/gentoo-guis</irc>
> > >
> > 
> > Though a freeform text field is probably better for humans, I'd
> > suggest having more explicit data available as an option, ie:
> > 
> > <irc network="irc.freenode.org" channel="#gentoo-guis">Channel
> > #gentoo-guis on the freenode network</irc>
> +1 on this.
> 

... and just when I was beginning to think no one actually cared :) ...

The proper form of an irc url is in my example
"irc://irc.gentoo.org/gentoo-guis" and I took it from gentoo's irc
channel page at http://www.gentoo.org/main/en/irc.xml .

That would mean limiting a single <irc></irc> field to just valid url's
just like the <homepage></homepage> field.

<irc>irc://irc.gentoo.org/gentoo-guis</irc>

The other thing I find with your example is that layman no longer uses
that old style of xml.  It still supports it, if you have that format
for some overlay definitions.  But does not fit the current
repositories.xml format.

Personally I would find it quite simple to use a reg expression to
extract a valid irc url from a mixture of written text and url.
<irc>#gentoo-guis on the freenode IRC network, irc://irc.gentoo.org/gentoo-guis</irc>

So far there is not a gui for working with layman, so is all command
line, including the output of layman -i some-overlay.  Don't get me
wrong, I have nothing aginst a layman gui.  I actually ended up taking
over layman's development because of it's lack of a good api for other
apps to use.  Namely porthole.  Plus I fully intend to create a
standalone gui for layman.

Would it be better that I create 2 irc sub data types then? 

<irc>
    <description>#gentoo-guis on the freenode IRC network</description>
    <url>irc://irc.gentoo.org/gentoo-guis</url>
</irc>

So far it seems many/most systems do not come setup to recognize and
take proper action for irc:// mime types like they do for http://

-- 
Brian Dolbec <dolsen@gentoo.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-03-13  8:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11  9:09 [gentoo-dev] Proposal: New irc data field in layman's repositories.xml file format Brian Dolbec
2012-03-12  7:52 ` Kent Fredric
2012-03-12  8:49   ` Robin H. Johnson
2012-03-13  8:33     ` Brian Dolbec [this message]
2012-03-13 10:36       ` Jeroen Roovers
2012-03-13 10:45       ` Robin H. Johnson

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=1331627608.29064.88.camel@big_daddy.dol-sen.ca \
    --to=dolsen@gentoo.org \
    --cc=gentoo-dev@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