On Tuesday 05 September 2006 23:14, Patryk Zawadzki wrote:
> How do we handle things like totem? It used to provide one file named
> totem_mozilla.so. Now it provides:
>
> [EMAIL PROTECTED] ~]$ rpm -ql browser-plugin-totem
> /usr/lib/browser-plugins/libtotem-basic-plugin.so
> /usr/lib/browser-plugi
How do we handle things like totem? It used to provide one file named
totem_mozilla.so. Now it provides:
[EMAIL PROTECTED] ~]$ rpm -ql browser-plugin-totem
/usr/lib/browser-plugins/libtotem-basic-plugin.so
/usr/lib/browser-plugins/libtotem-basic-plugin.xpt
/usr/lib/browser-plugins/libtotem-complex
On Tue, 5 Sep 2006, Elan Ruusamäe wrote:
> > > > now setup (which normlly should be the first package installed)
> > > > requires postshell which is in glibc (this one requires many
> > > > things), maybe it would be possible to move env-update to some
> > > > trigger, or create separeted packag
fixed in env-update-1.6.14-3
On Tuesday 05 September 2006 21:05, Tomasz Mateja wrote:
> [EMAIL PROTECTED] ~]# chmod 644 /etc/*.env
> [EMAIL PROTECTED] ~]# ls /etc/*.env -la
> -rw-r--r-- 1 root root 211 Sep 5 19:43 /etc/csh.env
> -rw-r--r-- 1 root root 213 Sep 5 19:43 /etc/profile.env
> [EMAIL
On Tuesday 05 September 2006 17:58, Paweł Gołaszewski wrote:
> On Tue, 5 Sep 2006, Elan Ruusamäe wrote:
> > > now setup (which normlly should be the first package installed)
> > > requires postshell which is in glibc (this one requires many things),
> > > maybe it would be possible to move env-upda
[EMAIL PROTECTED] ~]# chmod 644 /etc/*.env
[EMAIL PROTECTED] ~]# ls /etc/*.env -la
-rw-r--r-- 1 root root 211 Sep 5 19:43 /etc/csh.env
-rw-r--r-- 1 root root 213 Sep 5 19:43 /etc/profile.env
[EMAIL PROTECTED] ~]# env-update
[EMAIL PROTECTED] ~]# ls /etc/*.env -la
-rw--- 1 root root 211 Sep
On Tue, 5 Sep 2006, Elan Ruusamäe wrote:
> > now setup (which normlly should be the first package installed)
> > requires postshell which is in glibc (this one requires many things),
> > maybe it would be possible to move env-update to some trigger, or
> > create separeted package/spec for posts
On Tue, Sep 05, 2006 at 04:24:40PM +0200, Jakub Bogusz wrote:
> Ukhm... postshell would require FHS (because of directories), FHS
> requires setup (because of %attr with non-root groups).
in setup.spec there already are files which go to /sbin/
--
Sparky{PI] -- Przemyslaw _ ___ _ _ .
On Tue, Sep 05, 2006 at 04:24:40PM +0200, Jakub Bogusz wrote:
> On Tue, Sep 05, 2006 at 04:21:27PM +0200, [EMAIL PROTECTED] wrote:
> > On Tue, Sep 05, 2006 at 05:19:03PM +0300, Elan Ruusamäe wrote:
> > > On Tuesday 05 September 2006 17:16, [EMAIL PROTECTED] wrote:
> > > > now setup (which normlly s
On Tue, Sep 05, 2006 at 04:21:27PM +0200, [EMAIL PROTECTED] wrote:
> On Tue, Sep 05, 2006 at 05:19:03PM +0300, Elan Ruusamäe wrote:
> > On Tuesday 05 September 2006 17:16, [EMAIL PROTECTED] wrote:
> > > now setup (which normlly should be the first package installed)
> > > requires postshell which i
On Tuesday 05 September 2006 17:21, [EMAIL PROTECTED] wrote:
> /me votes for postshell.spec
go ahead ;)
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
On Tue, Sep 05, 2006 at 05:19:03PM +0300, Elan Ruusamäe wrote:
> On Tuesday 05 September 2006 17:16, [EMAIL PROTECTED] wrote:
> > now setup (which normlly should be the first package installed)
> > requires postshell which is in glibc (this one requires many things),
> > maybe it would be possible
On Tuesday 05 September 2006 17:16, [EMAIL PROTECTED] wrote:
> now setup (which normlly should be the first package installed)
> requires postshell which is in glibc (this one requires many things),
> maybe it would be possible to move env-update to some trigger, or create
> separeted package/spec
now setup (which normlly should be the first package installed)
requires postshell which is in glibc (this one requires many things),
maybe it would be possible to move env-update to some trigger, or create
separeted package/spec for postshell ?
--
Sparky{PI] -- Przemyslaw _ ___ _ _ ..
14 matches
Mail list logo