On Wed, May 27, 2009 at 01:10:36PM -0700, Stephen Hahn wrote:
> 1. Metadata. I'd prefer to move the build-related tags from "info."
> to "build.". Specifically, I suggest
>
> build.tool "pkgbuild"
> net.sourceforge.pkgbuild,version "[value]"
>
> (although I could be convinced that "build.pkgbuild.version" is
> safe).
One thing I used when I was working on publication was to use the value of
a fixed-name attribute to build the value of another attribute
programmatically. That is, something like
build.tool=net.sourceforge.pkgbuild
net.sourceforge.pkgbuild,version=<value>
But since I'm not designing a build system that uses this data, it's hard
for me to recommend one method over the other.
> 3. Multi-component package names and src/. So, as an example from
> Rich's pending renames, we would see
>
> [ ... brokenness ... ]
>
> To avoid this, I'd suggest using a "-src" suffix instead.
>
> So
>
> developer/lua-src
> web/firefox-src
>
> would be my proposed naming pattern.
I know it's not been popular in the past, but I'll suggest the form
developer/lua/src
web/firefox/src
Since no one sane would ever name a package "src", there's no worry about
name conflict, and it fits the source package into the hierarchy more
sanely, IMHO. Then again, perhaps your thought was that it *should* stand
separately.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
