Hi.. On Thu, 2009-01-29 at 13:14 +0100, Marcus Meissner wrote:

...

The thing is that the first one is "owned" by libgnome and the second one is owned by gtk-doc. However, now, many packages don't need libgnome and still put files in /usr/share/gnome/help and it's bad to require the gtk-doc package at runtime only to have /usr/share/gtk-doc existing.

AFAIK, you don't need gtk-doc at runtime only to have /usr/share/gtk-doc existing. If a package has foo.bar under /usr/share/gtk-doc/ , that package would create /usr/share/gtk-doc/ if it didn't already exist.

Easy, a directory can be owned by multiple packages. Just files cannot..

True. But is this advised? Personally, I think multiple packages owning the same directory is not good. :-) -Suman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Thu, 29 Jan 2009 15:28:48 +0100, you wrote:

Even though this is true, the folder would not be removed when you remove the package. That's why it's not a clean solution.

It is removed as soon as the last package owning a directory is removed. In my eyes that is a clean solution.

I tend to the same direction, but in conflicting situations like this one I'd probably prefer having the directory owned by more than one package than not having it owned at all by the end.

It doesn't have to be conflicts, see it as a form of sharing. Take for instance Perl packages with names in the same object hierarchy (something like package::inspect::foo, package::inspect::bar and package:inspect::clouseau). These packages will share the package/inspect directories and it would remove flexibility if only one of them owned them. To solve such cases you'd need meta packages that do nothing more than own directories and that would imho quickly lead to an exploding number of packages. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Fri, 30 Jan 2009 08:51:15 +0100, you wrote:

You got it out of context.. shame on you.

Seems I somehow misunderstood what was being written.

The paragraph referred to the fact that the directory does not have to be owned in this case and RPM would create all required parent directories needed (true).

in THIS case, the parent directories won't be removed on removal of a package, as it is not owned by any (except if you happen to install such a package too...)

But this shouldn't happen! I haven't testet with the OBS, but our autobuild (predecessor of the OBS) will reject a package if it contains directories without an owner. So either your package owns a directory or one of the packages you depend on. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org