[oi-dev] bits from JDS to userland: Re: conflicting files, dependencies and moving spec files to oi-userland

[Milan Jurik]

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...