From: Stefan Jones <cretin@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>, gentoo-core <gentoo-core@gentoo.org>
Subject: Re: [gentoo-dev] Prelinking in Gentoo and interactions with portage
Date: 18 Nov 2002 22:39:35 +0000 [thread overview]
Message-ID: <1037659175.3053.38.camel@localhost> (raw)
In-Reply-To: <1037651472.3049.24.camel@localhost>
Hi ppl, I have make a draft version of the portage changes needed.
I am not a python programmer, or want to be! The code can be optimised a
bit but I believe that prelink was well programmed so all checks for
file type etc are best handled by C based prelink, as long as os.system
is fast.
I have created code which adds support for the FEATURE flag prelink.
If it exists it uses prelink to verify the md5sums.
Also it prelinks files as they are installed.
Most importantly it works for me! Happy testing!
code:
download from
http://cvs.gentoo.org/~cretin/portage.py
This is based on the latest CVS portage
TODO:
* Safety checks for existence of /usr/sbin/prelink
* optimise to minimise number of calls to prelink
* see if a less IO intensive md5sum method exists (of course it does!)
now to sleep .....
--
Stefan Jones <cretin@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-11-18 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 13:50 [gentoo-dev] Prelinking in Gentoo and interactions with portage Stefan Jones
2002-11-17 23:39 ` [gentoo-dev] Re: [gentoo-core] " Daniel Robbins
2002-11-18 0:19 ` Alexander Futasz
2002-11-18 12:21 ` david mattatall
2002-11-20 9:31 ` [gentoo-dev] " Javier Marcet
2002-11-18 14:53 ` [gentoo-dev] " Felipe Ghellar
2002-11-18 17:41 ` David Olsen
2002-11-18 20:31 ` Stefan Jones
2002-11-18 22:39 ` Stefan Jones [this message]
2002-11-19 20:49 ` [gentoo-dev] " Stefan Jones
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=1037659175.3053.38.camel@localhost \
--to=cretin@gentoo.org \
--cc=gentoo-core@gentoo.org \
--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