Danek Duvall wrote:
On Wed, Jul 22, 2009 at 10:03:07PM -0500, Shawn Walker wrote:
(ignoring the fact that python 2.4 can't parse microseconds in ISO-8601
dates for datetime objects despite the fact that the standard allows
them).
Do future versions? We'll be running 2.6 soon enough, I hope.
Yes, it appears strftime in python 2.6 finally supports this:
http://docs.python.org/library/datetime.html#strftime-behavior
The point of /var/pkg/publisher is that metadata, other than catalog
data, will eventually be stored on a per-publisher basis. So, instead of
having /var/pkg/catalog /var/pkg/<metatype1> /var/pkg/<metatype2>, I'm
just organising this a bit more.
To be clear, the intent is really:
/var/pkg/publisher/<prefix>/
But, it probably should be:
/var/pkg/publisher/<prefix>/catalogs/
What other non-catalog metadata do you see going there?
A p5i file essentially matching the publisher/0/ output from a
repository. See bug 6898.
- For performance reasons, the client api will also store
versions of each of the catalogs proposed that only
contain entries for installed FMRIs to accelerate common
client functions such as info, list, uninstall, etc.
Does/could this eliminate the need for /var/pkg/state/install, as well?
And the "installed" files.
It does.
And by that, will it be part of the initial wad, or come some time later?
Initial; proposal has been updated to reflect.
It was discovered that the likely reason for poor serialization on
some SPARC systems is that simplejson uses a recursive function-
based iterative encoder that does not perform well on SPARC systems
(due to register windows?).
We have a workaround now, but we should probably file a bug on this and
possibly work on an implementation that isn't recursive.
Where should that bug be filed?
On the Python bug tracking system.
Will do.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
