On Mon, Apr 7, 2008 at 11:24 PM, Danek Duvall <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 07, 2008 at 10:05:00PM -0500, Shawn Walker wrote:
>  > >  |     opensolaris.source_url
>  > >  |         A URL to the source code bundle, if appropriate, for the 
> package.
>  > >  |
>  > >  |     opensolaris.repository_url
>  > >  |         A URL to the source code repository, if appropriate, for the
>  > >  |       package.
>  > >  |
>  > >  |     opensolaris.repository_changeset
>  > >  |         A changeset ID for the version of the source code contained in
>  > >  |       opensolaris.repository_url.
>  >
>  > I'm concerned that the above attributes aren't flexible enough to deal
>  > with packages that may contain work from multiple repositories or
>  > sources.
>  >
>  > It might better to provide a more free-form way to record this information.
>  >
>  > Also, assuming a single repository_changeset implies a certain kind of
>  > source control system technology being used. Multiple changeset ids
>  > may apply depending on the system.
>
>  There are a number of folks who have in the past indicated interest in
>  wrapping a build system around IPS, a la rpmbuild.  They're the ones who
>  need to chime in here and suggest what attributes they need.  I'd suggest
>  that until they do, we shouldn't make these part of the spec.

Having this information can be useful beyond just building the
packages.  I often times read the source when I am debugging issues -
particularly if I am writing dtrace scripts using the fbt provider.
Being able to read the exact version of the code is much more helpful
than reading something that you think is about right.  There have been
several times where this leads me to pointing to exact lines of source
as part of service requests or bug reports.  Sometimes it even turns
into a fix I contribute...

-- 
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to