On Mon, 2011-03-07 at 10:54 -0800, Danek Duvall wrote:
> > Removing linted would be more contentious, for example in the case where
> > a user uploads a new package, then tries to lint the entire repository:
> > the repo would report errors on unrelated packages that were previously
> > intentionally bypassed, for whatever reason.
>
> Well, I think of a repository as a place for packages where clients can
> access them. I suppose there's a case to be made that they're also an
> intermediate holding area for packages while they're still under
> development.
Sure.
> Perhaps we stress that stripping these attributes may not be
> desirable when publishing to the latter, but strongly encourage doing so
> when publishing to the former (possibly by using pkgrecv with a mogrify
> filter to do that publication).
It does mean that a random published manifest can't necessarily be used
as an example of packaging best practices if it's not clear which lint
errors are accidental, and which were known about and waived at the time
of publication.
> > > Another option might be to give pkgsend the ability to read in transforms
> > > from one or more files.
> >
> > Yes! I'd wanted that in the svr4 convert work to allow transforms to
> > automatically tag SMF services and the like -- can I resurrect that bit
> > of code too?
>
> I thought (not having looked at your code) that you were doing that, but
> hardcoding the ones you knew about, rather than providing a hook into
> pkgsend for people to provide arbitrary transforms.
The pkgsend changes I have out for review don't do transforms at all.
They do add some extra actions we've derived from pkginfo(4) contents,
but not using mogrify transforms. Making pkgmogrify into a module
would be pretty useful (as we could do more work on the new actions, eg.
automatically adding actuators to files previously delivered under the
'manifest' SVR4 class)
The svr4convert prototype shipped it's own private set of mogrify
transforms in a file, but didn't let users add their own (other than
editing that file: there was no intentional interface to let them run
arbitrary transforms)
I can certainly work on making pkgmogrify into a module once I've got
the sysrepo stuff out of the way. I'll file an RFE in the meantime.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
