On 06/10/10 10:48, Glenn Lagasse wrote:
Also, then where should these new pieces of infrastructure be
installed to?
No clue where python stuff ends up getting installed in ON.
Why wouldn't we just continue using the
vendor-packages/osol_install location?
We probably should, maybe even rename it vendor-packages/install.
Checking the ON source, it does seem that stuff gets delivered under
vendor-packages (zfs for example).
In the ON SNAP bits I'm working on, I dropped the osol_install location
mostly because it didn't seem to follow existing convention
(zfs/solaris). So beadm's modules live under vendor-packages/beadm.
fwiw.
Long time ago, before we introduce osol_install, all the beadm's modules
does live under vendor-packages/beadm, and other install modules
such as the transfer module live under vendor-packages. As more and
more install related python modules are introduced, we decided to put them
all under a directory. It seems messy to have all these install related
modules under the vendor-packages directory.
I think that's when we moved beadm under osol_install as well.
As we eventually want to put everything back into ON, do we still
want to maintain the current structure in vendor-packages?
Alternatively, we do
pull out the applications, such as distro_const and text_install, and keep
osol_install subdirectory for the libraries. For example,
vendor-packages/beadm
vendor-packages/distro_const
vendor-packages/osol_install/engine
vendor-packages/osol_install/doc
...
Thanks,
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
