public inbox for gentoo-user-de@lists.gentoo.org
 help / color / mirror / Atom feed
From: Juergen Rose <rose@rz.uni-potsdam.de>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de]
Date: Mon, 22 Jun 2009 10:49:33 +0200	[thread overview]
Message-ID: <1245660573.1188.0.camel@condor.homenet> (raw)
In-Reply-To: <010501c9f313$a07bdcd0$e1739670$@de>

Am Montag, den 22.06.2009, 10:29 +0200 schrieb Jörg Reisslein:
> Hallo NG,
> 
> ein Bekannter hat mich gebeten, an seinem gentoo-server die libxml2
> zu aktualisieren, da die derzeit verwendete Version angeblich Probleme
> mit Umlauten hat.
> 
> Da ich mich mit dem Gentoo-Paketmanager nicht auskenne (ich hatte bislang
> nur mit Debian und SuSE Systemen zu tun), meine Frage(n) an euch ;) 
> 
> -wie zeigt man die verwendete Version von libxml2 bei Gentoo an? (also 
> analog zu einem 'dpkg -l libxml2*' oder 'aptitude show libxml2')
> -wie aktualisiert man die Version über den Paketmanager (emerge ... )?
> -generell: falls das obige nichts bring und ich eine aktuelle Version 
> manuell kompilieren muss (configure-make-make install), wie verlinke ich 
> denn die neu kompilierte Version richtig? Sie sollte dann ja in
> /usr/local/lib
> liegen und müsste mit einem 'ldconfig' in den /etc/ld.so.cache aufgenommen
> werden oder?
> 
> vielen Dank für die Hilfe!
> 
> grüße
> Jörg


z.B. mit 'emerge -pv libxml2'.

Juergen





  parent reply	other threads:[~2009-06-22  8:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22  8:29 [gentoo-user-de] Jörg Reisslein
2009-06-22  8:48 ` [gentoo-user-de] Sebastian Beßler
2009-06-22 16:59   ` AW: [gentoo-user-de] Jörg Reisslein
2009-06-22 17:06     ` Jan Kohnert
2009-06-22 17:34       ` Sebastian Beßler
2009-06-23  7:07         ` AW: " Jörg Reisslein
2009-06-22  8:49 ` Juergen Rose [this message]
2009-06-22  8:53 ` [gentoo-user-de] Simon Braunstein
  -- strict thread matches above, loose matches on Subject: below --
2015-05-22  8:11 [gentoo-user-de] Gerhard Gössl
2015-05-23 21:08 ` [gentoo-user-de] Randolph Maaßen
2013-05-01 11:59 [gentoo-user-de] Erhard
2013-05-01 12:31 ` [gentoo-user-de] Marc Joliet
2013-05-01 12:32 ` [gentoo-user-de] Marc Joliet
2010-03-07 17:36 [gentoo-user-de] Pablo Alemán
2008-09-08 14:04 [gentoo-user-de] Chefkoch
2008-09-05 20:44 [gentoo-user-de] Chefkoch
2008-05-26 11:16 [gentoo-user-de] Florian Wallburg
2008-05-26 10:41 [gentoo-user-de] David Noelte
2008-02-22 10:02 [gentoo-user-de] Udo.Gerhards
2008-02-22 10:28 ` [gentoo-user-de] Arnold Krille
2008-02-22 10:31   ` [gentoo-user-de] Marc
2008-02-22 10:40     ` [gentoo-user-de] Arnold Krille
2008-02-22 10:51       ` [gentoo-user-de] Marc
2008-02-22 10:54   ` [gentoo-user-de] Tobias Hommel
2007-09-19 11:27 [gentoo-user-de] dennis
2007-06-18  7:08 [gentoo-user-de] Fabian Born
2007-03-23 12:45 [gentoo-user-de] Reimund Klain
2006-02-17 15:46 [gentoo-user-de] Jörg Vorher
2005-11-25 14:43 [gentoo-user-de] Mirko Hufnagel
2005-11-11 16:41 [gentoo-user-de] Andreas Mandalka
2005-11-13 17:50 ` [gentoo-user-de] Jan Girlich
2005-10-20 15:26 [gentoo-user-de] Alexander Fedorov
     [not found] <1120592286.1849.0.camel@cheetah.homenet>
     [not found] ` <1120604906.345.24.camel@koechlinux.ch>
2005-07-06 21:40   ` [gentoo-user-de] Juergen Rose

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=1245660573.1188.0.camel@condor.homenet \
    --to=rose@rz.uni-potsdam.de \
    --cc=gentoo-user-de@lists.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