On Thu, Oct 28, 2010 at 09:51:02AM +0100, Simon Marlow wrote:
> >>custom data stored in ghc's package database. For now this will be
> >>just another field `distPackageId'
> >
> >I think "localInfo" would be a better name. Just a free text field
> >people can put whatever they like in.
First: sorry for the delay. I managed to lock myself out of my box
at home during the OpenBSD ports hackathon in Budapest, so I hadn't
access to my Mails at home (and am now still catching up with my
mails). Stupid me ;-)
Next: I commited a patch (local to OpenBSD) in our ports tree where
this field is called `pkgpath'. Probably not appropriate for a
general solution, so I'll make some darcs patches (against ghc-head)
this weekend with the field called `localinfo' for now. Just for
discussion.
Of course, I managed to change the Cabal API, which in turn broke
the glib package and probably other packages using gtk2hs-buildtools.
I'm currently repairing this (for OpenBSD).
> I seem to recall there was a suggestion in the past to have a list of
> key-value pairs for each package, for OS-specific or
> local-installation-specific information. That would be more general
> than just having a single field, but there might need to be some
> convention for what to call the keys to avoid accidental clashes.
If I find the time, I'll try to work on some kind of sub-fields,
for example:
local-info:
foo: green,
pkgpath: devel/hs-glib,
...
May be tricky to parse. If all else fails, key/value pairs could be
represented as `key = value', i.e.
local-info:
foo = green,
pkgpath = devel/hs-glib,
...
We'll see.
Ciao,
Kili
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
