public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philippe Namias <pn@novadeck.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] more gnome-apps ebuild (and resend blufish ebuild)
Date: Wed Mar 14 09:26:02 2001	[thread overview]
Message-ID: <01031417255805.08719@cerberus> (raw)
In-Reply-To: <3AA64BC5.362D817@gottinger.de>

On Wednesday 07 March 2001 15:55, you wrote:
> Philippe Namias wrote:
> > > Thank you philippe,
> > >
> > > Can you take care that all you ebuild's install man and info pages to
> > > /opt/gnome/share/{man,info} and that
> > > etc stuff goes into /etc/opt/gnome. These are the places FHS2.1 uses.
> > > Stuff like ssh, pam, bonobo, readline, nls (gettext) support should be
> > > only build-in if the USE flags are set.
> >
> > Ok i will do as you said. I will give a try to gnome 1.4. beta 2 tonight
> > and report bug if any (but i am sure any as you done it:)
>
> I'm sure there are bugs in the dependencies. I will test them after I'm
> finished with updating.

I compiled gnome 1.4 (no dependancy problem) i just foud some missing headers 
in packages so i email to the maintainer of the package.
But globally gnome-1.4 is slow like the hell when running with nautilus 0.8.2 
(my workstation : a Bi-Processor PIII-800 with 512Mo ) but the funny part of 
it, is that gnome-1.4 start a lot faster than gnome1.2 .

>
> > > I commited gnome-base packages for gnome-1.4_beta2. You can take a look
> > > into current-packages.rc4 how
> > > far I am. Maybe you want to give it a try. It uses nautilus instead of
> > > mc. I'm working on a mozilla package
> > > that nautilus can link against at the moment.
> >
> > Great so i we can link also Galeon to it :)
>
> Yes once I found the correct c++ flags for mozilla. :-)
>
> > Tomorrow I will go on with
> >
> > > gnome-libs/gnome-apps stuff. We still
> > > miss alot of realy basic gnome packages.
> >
> > We are filling the gap slowly but surely
> >
> > Next i will do kde apps
>
> I already did kde-i18, kdesupport, kdelibs and kdebase. I think Daniel
> made a few updates too.
>
> I will focus on sgml/xml stuff after gnome.
>
> achim~
>
> > Thanks
> >
> > > achim~
> > >
> > > _______________________________________________
> > > gentoo-dev mailing list
> > > gentoo-dev@gentoo.org
> > > http://www.gentoo.org/mailman/listinfo/gentoo-dev
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://www.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev



  parent reply	other threads:[~2001-03-14 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06  3:27 [gentoo-dev] more gnome-apps ebuild (and resend blufish ebuild) Philippe Namias
2001-03-06 11:30 ` Achim Gottinger
2001-03-07  7:39   ` Philippe Namias
2001-03-07  8:21     ` Achim Gottinger
2001-03-07 11:10       ` Pete Gavin
2001-03-07 12:52         ` Achim Gottinger
2001-03-14  9:26       ` Philippe Namias [this message]
2001-03-15  7:07         ` Achim Gottinger
2001-03-20  8:43           ` Philippe Namias
2001-03-20 19:15             ` Achim Gottinger
2001-03-21  4:24               ` Philippe Namias
2001-03-21  7:03                 ` Achim Gottinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01031417255805.08719@cerberus \
    --to=pn@novadeck.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox