on) conditional, and it should be the easiest…
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
the
conversion myself, it's probably going to take me less time that it'd
take to explain and get someone else to do it.
Doubts? Comments?
[1] http://blog.flameeyes.eu/2010/12/01/the-automake-and-libtool-clash
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file
And just to add another reason, automake 1.8 already starts triggering
warnings with Perl 5.12. How soon do you fare that a Perl update will
make older automake fail altogether?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what
is structured).
Please let's not keep adding stuff to sys-* when it's not really
required for the system.
FWIW personally I'm not happy with having llvm there either. But I'd
also avoid pointless pkgmoves…
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail
thinking of is having some sort of maintainernotes element,
but not a passive one that has to be tested for, rather something that
repoman would spit out on the terminal when doing a scan/full.
Comments?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file
dependency not to
be found in the (well, missing) dependencies, it really doesn't make me
feel tremendously happy.
Thank you very much,
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http
[2]
http://blog.flameeyes.eu/2009/10/27/a-shared-library-by-any-other-name
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description
implementations). And if you do enable it, the USE flag you need is
cpudetection (already used by ffmpeg, mplayer and
jack-audio-connection-kit).
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http
stop.
In most cases, this sounds fishy and almost a hack deemed to failure so
my default vote would be do not expose this functionality to the user.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital
number?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
some backoffice ways to access it that reduce loads often enough…
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
are expensive
operations especially for those of us who use binary packages :)
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description
) for it.
This would exclude all plugin .la files which are also NOT NEEDED in
most cases.
And I'm starting to get angry at people who install .la files for PAM
modules… or Ruby extensions… or Python modules… and so on so…
_Most of them must die on a package-by-package basis._
--
Diego Elio
/2009/09/28/removing-la-files-for-dum-w-uncertain-people
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
).
- For pam, ruby or perl I have no idea :-(
find $(get_pammoddir) -name '*.la' -delete
find /usr/$(get_libdir)/ruby -name '*.la' -delete
Nothing fancy, just delete them ;)
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's
it, it
is installed in the Python tree and Python does not use .la files.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
they hit the tree, as the audit is already
complex enough on its own.
[1] http://blog.flameeyes.eu/tag/rubyng
[2] http://blog.flameeyes.eu/2010/10/24/anybody-hiring-me-for-pam
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what
the beta version is, so it's up to the
maintainer deciding that. Sometimes .0 versions are just as bugged as
_beta for others.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http
loader.
The link above would be fine though, just let it link as libv8.so, and
then be loaded as libv8-1.2.3.so.
References:
http://blog.flameeyes.eu/2009/10/27/a-shared-library-by-any-other-name
http://blog.flameeyes.eu/2010/10/08/linkers-and-names
--
Diego Elio Pettenò — “Flameeyes”
http
of dependencies is already in place,
we most certainly have no intention on going on to change it on all the
packages, so the '.' is totally useless for our scope.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's
-headers, but Mike dropped it with 2.6.35 to stay as close to
upstream as possible.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description
, the reason
_is_ the one above.
What is it, next time you're going to ask us to make ChangeLog stating
Version bump, because upstream released a new version?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG
support but it was not enabled by default.
Older GCC versions, such as the GCC 3.x series will be obsoleted;
problems arising on those versions, but not applying to GCC 4.4.4-r2
will not be fixed, so please update to the new version.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu
Il giorno dom, 10/10/2010 alle 15.45 +0100, Markos Chandras ha scritto:
app-backup/rsnapshot
I guess I can (co-)maintain this as I'm using it a few systems already.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what
or are you just going to quote Richard
again and propose choice for choice's sake?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description
://blog.flameeyes.eu/2010/10/04/libtool-archives-and-their-pointless-points
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description: This is a digitally signed
Il giorno mar, 05/10/2010 alle 13.25 +0200, Diego Elio Pettenò ha
scritto:
Definitely not from /usr/lib/libGL.la given that libGL is part of mesa
and mesa did not use libtool for linking until very recently,
Actually, scratch that, mesa IS NOT USING LIBTOOL AT ALL.
So you hit the jackpot: you
by 81.93.255.6
cvs [update aborted]: end of file from server (consult above messages if
any)
have you got to restart nss caches by chance?
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http
. They
are not.
They are a legacy of older operating system and static linking notions;
they are also not magical enough as they are only consumed back by
libtool. And not all the packages out there use libtool to link the
final application even if they were to use autotools.
--
Diego Elio Pettenò — “Flameeyes
don't, unless somebody's going to hire me to, and I'm dead
serious), lafilefixer could be improved, and quick-stabled together with
the new portage in case, so that it saves the modified metadata in the
VDB.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file
to propagate this change in package on users is necessary in this
case. Please, bump revision.
You still need to run python-updated (oh joy) so it probably isn't
strictly required.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what
for no reason.
It won't hurt anyway, and it'll definitely avoid people having to re-run
lafilefixer manually from time to time.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http
might require another
run of it, I don't think it makes much difference though to them —
beside making you feel righteous at dragging your feet. Nice try.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital
to deal with new packages,
showing how to identify pointless .la files that only increase the
number of them installed and cause false positives… and I'm still told
that a) I haven't done _enough_, as I had to prepare a master plan of it
and b) I'm too negative about stuff.
--
Diego Elio Pettenò
guess you're
right about that.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description: This is a digitally signed message part
not an accessible path at all_.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
on the matter and is up-to-date with
the situation last I knew.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
use is running the repoman commit — for a while when I
tried to run a stable system is what I have done.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
through without errors.
Thank you.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/
quick and easy to
identify; if you can bring up _any_ example of unfixable or
difficult-to-fix code, feel free.
I don't think that was not explained by me, I even wrote a whole blog
post about identifying, tracking down and fixing _FORTIFY_SOURCE
warnings.
--
Diego Elio Pettenò — “Flameeyes”
http
commit
you can as well not add it in the first place.
Can't you just write Version bump and cleanup?
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
signature.asc
Description: This is a digitally signed message part
ldflags by
taking the bugs that I report with forced --as-needed, take out those
reported for LDFLAGS=-Wl,--as-needed as well: what remains is usually
stuff that uses filter-ldflags or simply ignores the LDFLAGS variable.
Not all of them, but some of them for a start.
--
Diego Elio Pettenò
it.
Because such negative tests don't get far away: a single package failing
will drop its whole deptree from merging. And we have much more
important things to look for with a tinderbox than this, given the
amount of (failure) builds you'd be expected to see with this approach.
--
Diego Elio Pettenò
501 - 544 of 544 matches
Mail list logo
