From: Pieter Van den Abeele <pvdabeel@vub.ac.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] cracklib
Date: Sat, 27 Apr 2002 14:38:07 +0200 [thread overview]
Message-ID: <200204271251.g3RCpjW22432@excalibur.skynet.be> (raw)
In-Reply-To: <20020420123221.927CFAC7A2@chiba.3jane.net>
On Saturday 20 April 2002 14:27, you wrote:
> On Saturday, 20. April 2002 11:04, you wrote:
> > Hi,
> >
> > Is there a special reason why precompiled dict files are needed for
> > cracklib? Wouldn't it be better if we just added a sys-libs/words
> > ebuild that installs word-files that are used by the cracklib
> > installation to compile its own dict files, instead of including
> > precompiled dict files for all platforms?
> >
> > PPC is currently using this solution:
> > http://ftp.sunsite.dk/projects/gentooppc/portage/sys-libs/cracklib
> > http://ftp.sunsite.dk/projects/gentooppc/portage/sys-libs/words
>
> oh man - if been looking for this. what other package provides
> /usr/dict/words?
sys-apps/miscfiles provides /usr/share/words
I would like to know if it is ok if I replace gentoo-x86/sys-libs/cracklib
with gentoo-ppc/sys-libs/cracklib...
Gentoo PPC's cracklib can be found here:
http://ftp.sunsite.dk/projects/gentooppc/portage/sys-libs/cracklib/
What we're doing is removing the procompiled dict files in ${FILESDIR} and
have cracklib compile it's own dict files using the word lists provided by
sys-apps/miscfiles.
Cracklib is a critical ebuild, so I would like some reviewing first. Anyone
care to comment on this?
Pieter
--
Pieter Van den Abeele
pvdabeel@gentoo.org - pvdabeel@vub.ac.be
next prev parent reply other threads:[~2002-04-27 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 9:04 [gentoo-dev] cracklib Pieter Van den Abeele
2002-04-20 12:27 ` Thilo Bangert
2002-04-27 12:38 ` Pieter Van den Abeele [this message]
2002-04-27 13:28 ` Thilo Bangert
2002-04-27 14:32 ` Pieter Van den Abeele
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=200204271251.g3RCpjW22432@excalibur.skynet.be \
--to=pvdabeel@vub.ac.be \
--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