Jason Helfman <j...@freebsd.org>:
On Wed, Nov 13, 2013 at 11:30 PM, Erwin Lansing <er...@freebsd.org> wrote:
On Wed, Nov 13, 2013 at 04:47:20PM -0500, Eitan Adler wrote:
> On Wed, Nov 13, 2013 at 3:27 PM, Melvyn Sopacua <mel...@magemana.nl>
wrote:
> > On Wed, 13 Nov 2013, Kris Moore wrote:
> >
> >>
> >> Wanted to run this by the ports community, see your thoughts. We build
> >> our PBIs from the ports system, and are able to parse most of the
> >> information out for display graphically, like descriptions,
maintainers,
> >> website, License, etc. However we currently don't have a way to pull
the
> >> actual name of the upstream vendor / author. I.E. for Firefox the
vendor
> >> would be "Mozilla".
> >
> >
> > WWW: [Mozilla](http://www.mozilla.org/)
> >
> > So, markdown format in pkg-descr. Seems the least amount of work?
>
> This adds a lot of work to the parser.
>
> IMHO we should have VENDOR_WWW and possibly VENDOR_NAME in the port's
> Makefile. It should not be hard to automate this for VENDOR_WWW since
> we already have the WWW: lines in pkg-descr.
>
That sounds like an excellent idea. I'm just a bit worried about
spreading the information over too many places, and would rather split
content from logic and add these to pkg-descr as well next to the
current WWW. I know we're not consistent already with things like
COMMENT and LICENSE already in the Makefile, so won't ojbect too much to
where these end up.
Erwin
With good ideas usually bloat is not too far behind. I think this is a
great idea, however I think it would be
worth considering a potential new file for this, that can be parsed without
causing too much new data in existing
files. Perhaps, a file named pkg-vendor. In this file, all sorts of
information can be places, and parsed or used
by our package infrastructure.
I like that idea, but how about carrying it on a bit to enable more metadata,
such as Trove categorization, generic descriptions, links to relevant
sites of interest for the port, etc.pp.
Instead of pkg-vendor, I'd name it pkg-meta or so and something like
the following
comes into mind:
VENDOR: '
NAME : Vendor
WWW : UrlOfVendor
'
UPSTREAM: '
CONTACT : UpstreamDeveloperContact
BUGS : LinkToUpstreamBugTrackerOrWhatever
CHANGELOG: LinkToUpstreamChangeLog
'
CLASSIFICATION: '
trove classifiers here
'
LINKS: '
DOC : LinkToOnlineReference
DOC : OtherLinkToOnlineReference
RELATED : LinkToRelatedProjectOfRelevance
COMMERCIAL : LinkToCommercialSite/Support/whatever
YOURIDEAHERE : ..
'
Personally, I would not want to see that being parsed by some make-compatible
implementation, but would rather see some supplementary script in
Tools/ or something
else to deal with this. Especially to avoid keeping the format limited
to cope with
the limitation of make and sh.
Since the meta information are not necessary by the ports
infrastructure (as pointed
out earlier), supplementary third-party tools and projects can and
should deal with it.
Cheers
Marcus
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
