nstalled with user/group portage" one
is, but I don't think any of the others are.
My time is rather limited to do anything about it for a month or two,
but I thought I'd throw this into the melting pot for thought at least.
--
Kevin F. Quinn
signature.asc
Description: PGP signature
ge to the user having LC_* set apart from
LC_MESSAGES?
--
Kevin F. Quinn
signature.asc
Description: PGP signature
s is simpler in that it's just a few bash functions as
> opposed to more resolver foo.
There's a lot to be said for keeping things simple, of course :) It's
easy enough to mess up things like dep-graphs in any case - introducing
these sorts of dynamic dependencies can render it su
:
use.local.desc: boost: Use boost library for tr1 rather than gcc's.
ebuild:
...
inherit ... toolchain-funcs versionator ...
...
DEPEND=... boost? ( dev-libs/boost ) ...
...
pkg_env_check() {
use boost && return 0
version_is_at_least "4.1" $(gcc-version) && return 0
echo "Either USE boost, or switch to gcc later than 4.1"
}
(with a default definition, "pkg_env_check() { return 0; }" )
--
Kevin F. Quinn
signature.asc
Description: PGP signature
est when they do one job only. What you're asking for
is to embed the has_version check into built_with_use, which would
prevent built_with_use being used in any way other than the one you have
thought of.
--
Kevin F. Quinn
signature.asc
Description: PGP signature
is clearly
consistent. It's a simple enough concept; in your example you want
built_with_use to mean "package is installed and it was built with
USE=foo" whereas clearly there's nothing wrong with asking for "if the
package is installed, it needs USE=foo".
--
Kevin F. Quinn
signature.asc
Description: PGP signature
ll built_with_use until you know the
package is installed.
To put it into boolean logic, you want built_with_use to do:
AND
whereas others may want
IMPLIES
The correct answer is to use has_version to do the installed check,
built_with_use to do the USE=foo check and code the conjunction as
required.
--
Kevin F. Quinn
signature.asc
Description: PGP signature
ild and install
> machines are different.
If the main issue is cleaning up after an abort, perhaps it would be
useful to add a pkg_abort() phase to the package manager; then that can
be implemented in an eclass.
--
Kevin F. Quinn
signature.asc
Description: PGP signature
On Fri, 26 May 2006 02:28:44 -0400
Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Friday 26 May 2006 02:27, Kevin F. Quinn wrote:
> > On Thu, 25 May 2006 21:57:30 -0400
> >
> > Alec Warner <[EMAIL PROTECTED]> wrote:
> > > Attached is a tiny diff for mak
On Thu, 25 May 2006 21:57:30 -0400
Alec Warner <[EMAIL PROTECTED]> wrote:
> Attached is a tiny diff for make.conf, can someone with l337 skills in
> manpages look it over before it gets commited.
Easiest way to check how a man page looks is to do:
nroff -man | less
--
Ke
rds the original question about adding '--list
' to emerge, you can of course to package lists yourself anyway
as portage exists today. Just create a file with a list of atoms in
it, and do for example:
# cat | xargs emerge -puv
Doesn't get much easier than that - perhap
dir getportdir.c -lpython2.4
Does the equivalent of:
#!/usr/bin/portage
import portage;
print portage.settings["PORTDIR"];
(more or less). Docs on the API itself (which comes with Python) are at
http://docs.python.org/api/api.html
--
Kevin F. Quinn
#include
#include
int
st something like:
if [[ -n ${QA_STRICT_TEXTRELS} ]]; then
f=$(scanelf -qyRF '%t %p' "${D}")
else
filter version
fi
...
where we can add QA_STRICT_TEXTRELS to make.defaults.
--
Kevin F. Quinn
signature.asc
Description: PGP signature
On Sun, 5 Mar 2006 20:46:25 -0500
Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Sunday 05 March 2006 19:48, Kevin F. Quinn (Gentoo) wrote:
> > This could be done via the profiles, perhaps - package.qa, something
> > like package.mask/use/keywords:
>
> i hate such thin
holds true for one arch defiantly is not the case for others.
This could be done via the profiles, perhaps - package.qa, something
like package.mask/use/keywords:
net-dialup/slmodem QA_EXECSTACK="..." QA_TEXTRELS="..."
--
Kevin F. Quinn
signature.asc
Description: PGP signature
> those suckers a hell of a lot faster (the delay from switching
> versions is because the ld.so.cache is rebuilt)
Since switching gcc and binutils configs swaps out library directories
in ld.so.conf, isn't it necessary to rebuild ld.so.cache anyway?
--
Kevin F. Quinn
signature.asc
Description: PGP signature
On 3/11/2005 13:45:16, Brian Harring ([EMAIL PROTECTED]) wrote:
> Offhand, why isn't this a bashrc trick?
I took a cue from solar's autopatch bashrc stuff, and wrote the attached.
Sources whatever it finds in a sort of shell-file overlay that matches the
package being built and optionally the cur
17 matches
Mail list logo
