On 10/17/07, Laszlo (Laca) Peter <laca at sun.com> wrote: > > On Wed, 2007-10-17 at 01:29 +0200, Thomas Wagner wrote: > > On Sat, Oct 13, 2007 at 01:09:43AM +0530, Ananth Shrinivas wrote: > > [...] > > > Slightly off topic: How does IPS affect the SFE repository and the > > > pkgbuild tools ? As I understand IPS can import SVR4 packages. But > if > > > it has frozen specs for packaging metadata and data, should > pkgbuild > > > be enhanced to generate "native" IPS format packages ? > > > I am eager to help out with implementing these or other ideas. > > > Ananth > > > > near future: > > pkgbuild should be able to feed a personal/local_site repository > > with IPS packages or trigger the import. This would have two > > advantages: IPS-testing could be extended on non-Indiana packages > > and Indiana instantly could receive missing software we already > > have available in the SFE repository. > > Actually, I'm working on building SFE on the indiana prototype > (slim_install). I've got >500 packages built already and I'm > fixing up stuff as I go. It'd be even better to generate native > ipkg packages and publish them directly. > > Hey Laca,
Cool ! But from what I understand, IPS has no place for scripts. No class action, preinstall and postinstall scripts. And quite a few (100+) SFE spec files have %post and %preun sections. How are you handling this ? Should newer spec files start taking this into account and do things differently ? Cheers, Ananth -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20071017/5a54c22e/attachment.html>
