public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] more gnome-apps ebuild (and resend blufish ebuild)
Date: Tue Mar 20 19:15:02 2001	[thread overview]
Message-ID: <3AB8085F.B15800D0@gottinger.de> (raw)
In-Reply-To: 01032016461900.27294@cerberus

Philippe Namias wrote:
> 
> On Thursday 15 March 2001 14:39, you wrote:
> > Philippe Namias wrote:
> > > 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.
> 
> >
> > Can you tell me what packages miss headers?
> 
> So the package:
> 
> gal-0.5
> gconf-0.50
> oaf-0.6.4

Hmm, I can remember some problems like that. The cause is that the file
90gnome from the gnome-1.4_beta2 package must be installed first.
The packages you named compile without errors but can not find the other
gnome packages and do not add
the support for that. For example oaf needs ORBit support and gconf
gdkimlib.

This is a new problem. The older versions of ebuild resolved runtime
dependencies of a package after the package was merged. This did not
fully work because some packages require binaries from rdepend packages 
in their plk_postinst functions. So now rdependen packages get merged
first and after that the package.
Additionaly packages can now only be merged if all rdependencies are
resolved.

So in the old days (about a month ago) we simply merged the gnome-1.2
package first and after that all the gnome-stuff compiled without
problems.

There could be a workaround. If we make packages for the env-files and
add these env packages to the build/runtime dependencies of all gnome
packages the problems should be solved. But all the dependencies of
packages not installing into /usr and depending on an environment coming
from one of the /etc/env.d/ files
(beside 00basic) must be updated.

Comments please.
> 
> >
> > > 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 .
> >
> > Hmm, it runs slower that with mc but not slow as hell. :-)
> > On what arch did you build i486-pc-linux-gnu (-m486 -O2) are the
> > defaults in rc4_pre2.
> > I used i686-pc-linunx-gnu for testing over here.
> > Did you try to build nautilus with mozilla?
> > I think I found the right c++ flags and compilation works. Mozilla and
> > nautilus both run but the
> > embedded_mozilla component in nautilus allways segfaults.
> 
> I build it with -O2 -mpentium (arch=i686) but i find it slow but it's a beta
> so...
> I build nautilus with the gtkhtml component so i need to try with the mozilla
> embeded  component (i will take a look at this but the main problem is that
> mozilla get times to compile so i hope to have something till the end of the
> week.

:-) Mozilla needed about 2 1/2 hours here. It's a mess to experience
with such a package.

Anyone out there who want's to make a package for openoffice ?

> 
> >
> > I hope I have more time to spend to gentoo next week. This week I was
> > very busy with other works, so
> > sorry that I did not commit your packages yet.
> 
> That's ok Daniel Robbins granted me access to the CVS so i commit stuff
> myself.

Yes that is definately a good decision.

Welcome in the team.

achim~

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



  reply	other threads:[~2001-03-21  2:14 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
2001-03-15  7:07         ` Achim Gottinger
2001-03-20  8:43           ` Philippe Namias
2001-03-20 19:15             ` Achim Gottinger [this message]
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=3AB8085F.B15800D0@gottinger.de \
    --to=agottinger@t-online.de \
    --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