All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] cracklib: New package
Date: Thu, 4 May 2017 23:34:52 +0200	[thread overview]
Message-ID: <32863807-7cf4-75fc-1dd3-0e6f6517986e@gmail.com> (raw)
In-Reply-To: <1493881807.2302.3.camel@spectralink.com>

Hi Stefan, all,

Le 04/05/2017 ? 09:10, S?rensen, Stefan a ?crit :
> On Sun, 2017-04-30 at 15:36 +0200, Romain Naour wrote:
> 
>> +ifeq ($(BR2_PACKAGE_CRACKLIB_TOOLS),)
>>> +define CRACKLIB_REMOVE_TOOLS
>>> +	rm -f $(TARGET_DIR)/usr/sbin/*cracklib*
>>
>> Maybe this part can be done in a post install script instead ?
> 
> Post install script? I can't find any reference to what that is.

Sorry, I meant post build scripts, see BR2_ROOTFS_POST_BUILD_SCRIPT option.

> 
>>> +	rm $(TARGET_DIR)/usr/share/cracklib/cracklib-small
>>
>> Why do you remove cracklib-small binary ?
> 
> This is not a binary, but rather the source for the small dictionary.
> It is not needed on the target.

Ok, thanks for the explanation.

Best regards,
Romain

> 
> 
> Stefan
> 

  reply	other threads:[~2017-05-04 21:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  7:56 [Buildroot] [PATCH v3 1/2] cracklib: New package Stefan Sørensen
2017-04-19  7:56 ` [Buildroot] [PATCH v3 2/2] libpwquality: " Stefan Sørensen
2017-04-30 13:51   ` Romain Naour
2017-04-19 16:08 ` [Buildroot] [PATCH v3 1/2] cracklib: " Danomi Manchego
2017-04-30 13:36 ` Romain Naour
2017-05-04  7:10   ` Sørensen, Stefan
2017-05-04 21:34     ` Romain Naour [this message]
2017-05-05 12:33       ` Sørensen, Stefan
2017-05-04 21:19 ` Thomas Petazzoni

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=32863807-7cf4-75fc-1dd3-0e6f6517986e@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.