On Thu, Dec 06, 2007 at 02:22:23PM +0800, zhongyuan sun - Sun Microsystems - Beijing China wrote:
> So fay by my understanding, Indiana can only support adding package from > IPS. not any local package mechanism be supported. Not entirely true. The old sysv package tools will still be present and will work, so you'll still be able to run pkgadd to install a non-IPS package. But sysv packages won't participate fully in the dependency tree, won't be searchable with the IPS tools, and so on. > (1) Since there will be thousands of applications/drivers packages on the > IPS, how can the user know which package is a hardware driver especially > which chipset it intent to drive? will Indiana release some documents to > dress a driver package with its specfic hardware chipset. We need to figure this out. Bart and Jerry and I had a conversation about this, and it's clear that there's missing architecture here which the packaging system should be a part of. We'll be working with the devices team to make sure there's an interface that will return the information necessary to find out what packages contain drivers that might drive the device in question. We should be able to do better at this than we do today. > (2) How to handle 3rd party driver, if Indiana does not support SUNW > package format, do we expect 3rd party vendor will transfer their SUNW > driver package to new IPS format and building their own IPS server? Eventually, yes. We intend to make it easy for driver authors to convert their sysv packages to IPS, and if they're willing to allow their drivers to be redistributed, then anyone else can do that work for them, too. But the sysv package format can be used as a stopgap measure until everyone's comfortable with IPS and has time to learn to use it. > (3)If Iniana user boot system and find no network driver, the first > solution he/she will do is install network driver so can try other > feature. But if Indiana can not support installing local package file, > how to handle this scenario? We will support installing from a serialized copy of a package, but we don't currently. The workaround is to run a local copy of the server, which is pretty quick and simple to do. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
