Received: (at submit) by bugs.debian.org; 23 Jun 2001 16:09:13 +0000 From cactus@cactus.rulez.org Sat Jun 23 11:09:13 2001 Return-path: Received: from booster.telnet.hu [::ffff:212.75.128.38] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15Dpy8-0006kG-00; Sat, 23 Jun 2001 11:09:08 -0500 Received: from sendmail.telnet.hu ([212.75.128.13] ident=qmailr) by booster.telnet.hu with smtp (Exim 3.12 #1 (Debian)) id 15Dpxz-0001SR-00 for ; Sat, 23 Jun 2001 18:08:59 +0200 Received: (qmail 21549 invoked from network); 23 Jun 2001 16:08:51 -0000 Received: from isdn011.bp1.telnet.hu (HELO mail.cactus) (212.75.129.11) by mail.telnet.hu with SMTP; 23 Jun 2001 16:08:51 -0000 Received: from galaxy.cactus (really [10.0.0.3]) by mail.cactus via smail with esmtp id (Debian Smail3.2.0.102) for ; Sat, 23 Jun 2001 18:08:23 +0200 (CEST) Received: by galaxy.cactus via sendmail from stdin id (Debian Smail3.2.0.111) for cactus@cactus.rulez.org; Sat, 23 Jun 2001 18:08:16 +0200 (CEST) Message-Id: Date: Sat, 23 Jun 2001 18:08:16 +0200 (CEST) From: ERDI Gergo Subject: oaf: .oaf and .oafinfo files should not be in /usr/share To: submit@bugs.debian.org Bcc: X-Mailer: bug 3.3.9 X-BadReturnPath: cactus@galaxy.cactus rewritten as cactus@cactus.rulez.org using "From" header Delivered-To: submit@bugs.debian.org Package: oaf Version: 0.6.5-5 Severity: wishlist .oaf and .oafinfo files describe the location of binary component factories that are not necessarily available for all architectures in a given setup. i.e. if a central server is serving multiple clients of various architectures, component C1 for architecture A1 may not be available, yet the .oaf file for C1 is available to machines of A1 since they are in /usr/share which should be safely sharable among clients of multiple architectures. I propose moving .oaf files to /usr/lib/oaf. Beside this bug report, I am also currently rallying on gnome-components-list to have this fixed in upstream for GNOME 2.0.