Hi all, this has been silent recently, too silent ;-) Lets try to get some concrete action items we can work on. First step should be to have an overview over all packages the Invis server needs. In a perfect world, these should all be part of the openSUSE:Factory project as that garantees the best integration with the distribution. For packages that do absolutely not fit into Factory for what reason ever, I suggest to create the server:invis project in OBS and put them there. Later on, we can put the Kiwi-Image file, which is used to create the iso image of the openSUSE Invis Server, into the server:invis repo and let OBS create the image. In the ideal world we only would have the product kiwi file in server:invis. Is everybody agreeing on that? As a first action item, we should go through the list of packages installed through the Invis setup script and check if they are in Factory. If not, we should move them to Factory, or, as a second possibility, to server:invis. I created a list of packages some time ago which get directly installed by the Invis setup script (attached again). The list of packages which are not yet in Factory is comparably short: afio -> home:flacco ipcalc -> home:flacco smbldap-tools -> home:flacco php5-APC -> server:php:extensions php5-pear-mail -> server:php:applications phpMyAdmin -> server:php:applications We should try to push these to Factory. Anybody volunteering? A good read how that works is http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory Stefan, are there other packages needed? regards, Klaas