Danek Duvall wrote:
> I haven't checked to make sure it still applies since May, but I suspect
> that any necessary changes will be small, obvious, and easily reviewable.
> I suspect I'll want to make another change that will auto-generate (at
> least most of) the version-generic manifests, too, but that can be a
> separate change. I may work on that this weekend, and I'll put up a
> pyver-v2 if I get it done before any reviews come in.
Thanks, Rich, for taking a look at this. Here's an updated version that
not only emits all the version-specific manifests, but also the
version-generic manifest. It assumes all the metadata (set actions) are
the same, and junks everything else, adding the appropriate conditional
dependencies. If the generic package needs to have other things in it,
then you can create a -GENFRAG manifest (from "generic fragment"; this name
is also up for being changed) with other actions in it.
https://cr.opensolaris.org/action/browse/userland/dduvall/pyver-v2/
There are examples of converting both mako and mercurial. The former is
simple, the latter has a more complex generic package, with stuff in it.
The final mako manifests are identical pre- and post-change, aside from the
fmri timestamp, and the fact that the new generic manifest adds the ARC
case information. The final mercurial manifests are almost identical,
aside from the fmri timestamp and the various results of patching a .py
file at a different time. Plus the 2.7 version is brought in line with the
2.6 version, adding a couple of bypass-generate tags, and the dependency on
the python-generic package is now required instead of optional (I don't
know why either of these differences between the two packages exist).
I don't know why the mako manifests don't show up as renames, but I'll fix
that.
Thanks,
Danek
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
