public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Travis Tilley <lv@gentoo.org>
To: Andrej Kacian <ticho@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Two requests for ebuild maintainers+writers
Date: Fri, 03 Sep 2004 09:43:24 -0400	[thread overview]
Message-ID: <413874FC.8040807@gentoo.org> (raw)
In-Reply-To: <20040903013332.197052a3@thelair.ynet.sk>

Andrej Kacian wrote:
> On Wed, 25 Aug 2004 15:43:48 -0400
> Travis Tilley <lv@gentoo.org> wrote:
> 
> 
>>1) start using $(get_libdir) wherever possible instead of referencing 
>>lib directly. get_libdir is now part of the eutils eclass and is used by 
>>gen_usr_ldscript in eutils. so, where previously it had:
> 
> 
> Does this apply for python packages that install files in /usr/lib/python/... ?


I guess I should have clarified a bit. It applies to any non-binary-only 
non-bytecode non-script library. $(get_libdir) is there to make sure 
that 64bit libraries go into lib64 on amd64, and 32bit ones go into lib. 
or that N64 objects on mips go into lib64, N32 in lib32, and O32 in lib 
(at least i -think- that's how they eventually want it set up?).

The way python is currently patched, it -should- be looking in lib64 as 
well as lib, and using $(get_libdir) shouldnt change the behavior on 
non-multilib archs at all, so it wouldnt have hurt to use it... but i 
guess this is one case where it would make more sense to not use 
$(get_libdir). sorry about that ^^;


Travis Tilley <lv@gentoo.org>

--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2004-09-03 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 19:43 [gentoo-dev] Two requests for ebuild maintainers+writers Travis Tilley
2004-08-27 13:55 ` Paul de Vrieze
2004-08-27 16:51   ` Travis Tilley
2004-08-27 21:43     ` Paul de Vrieze
2004-09-02 23:33 ` Andrej Kacian
2004-09-03 13:43   ` Travis Tilley [this message]

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=413874FC.8040807@gentoo.org \
    --to=lv@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ticho@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