Hello, list. Will IPS have a method for building many packages with complicated dependencies at once, so that I won't have to do configure, make, make install a billion times. In example, lets say someone wants to create packages for GNOME and/or KDE. As we all know, these packages have many dependencies on external (not part of GNOME/KDE) and internal (part of GNOME/KDE) packages. Would it be possible to have an automated method for packaging many pieces of software for IPS all at once?
Also, in an unrelated issue, is IPS capable of supporting multiple versions of a package or library? Lets say I need two versions of Package-A. Can I install them in parrallel (using zones or some other mechanism for example)? Lets say the Package-B depends on Package-C-1.0.1 and Package-D depends on Package-C-2.0.2, and if it is mission-critical to have Package-B and Package-D installed, will IPS be able to install both packages and their dependencies without conflicts or breaking my system (using zones or some other mechanism)? Will IPS have a mechanism for extensions or plugins or scripts if a developer wanted to extend functionality without having to modify the core codebase? (not that I would want to do that, but I am curious :D ) Will IPS be able to install different builds of opensolaris ON consolidations in separate ZFS partitions/filesystems/etc. ? I heard that IPS will make use of the ZFS snapshot functionality for snapshots of installations. Why would I use IPS to make a snapshot of my packages, if I could use ZFS itself? Will I, as a system administrator, be able to decide which packages a user can or can't install on his account? I am pretty sure that the answer to this question is yes, but will IPS be aware of SMF? Thanks!
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
