On Thu, Oct 08 2015 16:23:35 -0400, Eric Sproul wrote: > On Thu, Oct 8, 2015 at 3:37 PM, Lauri Tirkkonen <[email protected]> wrote: > > % pkg list -Hv simplejson-26 > > > > pkg://omnios/library/python-2/[email protected]:20150402T184431Z > > i-- > > > > Yes, yes it is, and it *was* built using pkgsend -T '*.py'. However, > > the commit in omnios-build introducing that was authored on Mar 25 2015 > > (8cc8f3ef45d9c7d8ccdfda608d00599cd3890597). My theory is that if the > > file content does not change, even if pkgsend -T is used to preserve the > > timestamps, the file is not touched on update; would that help explain > > what you're seeing? > > Since .pyc files are evidently locally modified outside of pkg(5), > would it make sense to mark them as such in their manifests, i.e. > setting the "preserve" attribute? This makes pkg verify not report > differences from the installed manifest. > > Perhaps not a total win, though, as it would mean potentially losing > upgrade content, unless preserve was set to "renameold" or some such.
One could just not ship them at all; I was just trying to find out why they're being regenerated after the package install. -- Lauri Tirkkonen | lotheac @ IRCnet _______________________________________________ OmniOS-discuss mailing list [email protected] http://lists.omniti.com/mailman/listinfo/omnios-discuss
