> > > Additionally as a reference, below is the webrev of > the overall snap > > upgrade gate synced up against the current > slim_source base. > > > > > http://cr.opensolaris.org/~equach/webrev.SnapUpgrade > > I mentioned this on pkg-discuss: the Python module > doesn't seem right: > > - it shouldn't be installed in /usr/lib/, but at the > same location as
It's final destination once installed is /usr/lib/python2.4/vendor-packages/beadm. > other Python modules, namely > /usr/lib/python2.4/vendor-packages > - it should just be called 'libbe.so' as per other > Python modules I tried to find a definitive answer to the naming convention for C -> Python library wrappers but was unsuccessful. Can you point me to where the naming for wrappers is defined and I'll change libbe_glue to libbe? > > - I haven't looked, but what is the purpose of > libbe_glue.h? To declare the public functions in libbe_glue.c. Also follows the libbe.h convention. Thanks Tim > > regards > john > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-di > scuss -- This message posted from opensolaris.org