Hi Andrzej, On po, 2013-07-15 at 14:46 +0200, Andrzej Szeszo wrote: > Hi Milan > > I knew similar question will be asked sooner or later. >
so lets maintain the list of such packages at least. > If I had unlimited amount of spare time, I would convert all spec > files to userland style packages. It is not likely going to happen any > time soon, unfortunately. > > So, to make better use of everyone's free time, I think we don't have > a choice and will have to integrate JDS packages to oi-userland > somehow. Perhaps in a similar way as illumos-gate component. > I am not fan of userland build system, because I think its manifests lacks support for wildcards and maintaining large packages like some in desktop consolidation is nightmare. But your choice :-) Anyway, I am open to move many smaller non-desktop related bits to userland, many libs make no sense in JDS, also Python packages would be nice to move out of JDS. > Milan, would you be able to share your JDS build script(s) in case > someone would like to have a go at creating JDS component? > Here you can find my active copy of consolidation: http://hg.opensolaris.cz/oi-jds/ If you want to build bits for hipster, you should drop ncurses, Python and Python-extra, probably also xscreensaver from Makefile. CBE is same as for SFE. I am ready to answer questions. FYI, I am just testing newer build of JDS build on top of a8 dev-test. If it will be OK, I will ping you and you could import it to hipster if you want. I cannot build on top of hipster for now because I do not have so quick build machine with hipster installed. Best regards, Milan > Cheers, > > Andrzej > > > > On 12 July 2013 20:05, Milan Jurik <[email protected]> wrote: > > Hi, > > > > is there any process in place for moving bits from JDS to userland? I > > was thinking about possibility to update some JDS bits (with specs, of > > course). And I need to know which bits I could remove from JDS. Could > > anybody responsible for hipster release engineering talk to me about it? > > > > As for conflicting bits - gnome/locale/xxx should be obsoleted in > > hipster already so I do not know which conflict you see. But I did not > > try hipster yet so I have no idea what's broken there. > > > > Best regards, > > > > Milan > > > > On pá, 2013-07-12 at 20:23 +0400, Alexander Pyhalov wrote: > >> Hello. > >> I'm trying to import SUNWxscreensaver.spec to oi-userland. > >> The issue is that it is actually three different packages. I've almost > >> finished with xscreensaver itself, but there are also > >> xscreensaver/hacks, xscreensaver/hacks/hacks-gl and > >> xscreensaver/hacks/rss-glx. > >> The process of determining package boundaries is rather boring and > >> error-prone :) > >> > >> So, I came to the following: > >> now we ship xscreensaver.mo files in gnome/locale/XX packages, which (at > >> least gnome/locale/ru) by the way conflict with > >> gnome/accessibility/gnome-a11y-libs (on > >> usr/share/locale/ru/LC_MESSAGES/at-spi.mo), desktop/gtk2 (on > >> usr/share/locale/ru/LC_MESSAGES/gtk20.mo) and so on.... > >> > >> The question is following: if we build application on by-component > >> basis, how can we create global package like gnome/locale/XX ? Probably, > >> it can be converted to just meta-package with a lot of dependencies on, > >> e.g. xscreeensaver/locale/XX and so on. > >> > >> The other question is what to do with localization in this particular > >> case... > > > > > > > > _______________________________________________ > > oi-dev mailing list > > [email protected] > > http://openindiana.org/mailman/listinfo/oi-dev > > _______________________________________________ > oi-dev mailing list > [email protected] > http://openindiana.org/mailman/listinfo/oi-dev _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
