All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] rootfs_rpm.bbclass: rename postinst trigger script
Date: Sat, 03 Mar 2012 20:31:39 -0800	[thread overview]
Message-ID: <1330835499.3949.18.camel@ted> (raw)
In-Reply-To: <af77629ed96cb6c688540f19806558f6a8034771.1330796256.git.otavio@ossystems.com.br>

On Sat, 2012-03-03 at 17:39 +0000, Otavio Salvador wrote:
> Use 'run-postinsts' as trigger script name for consistency against
> package managers.
> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>  meta/classes/rootfs_rpm.bbclass |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)

I find the consistency argument a little confusing when you had to
rename this for all of the packaging backends from the same thing?

I understand you want a less confusing name though as configure is an
overloaded word.

Also, please do post the deb patch too. Saying you've just pushed an
extra patch somewhere doesn't really work...

Cheers,

Richard




  reply	other threads:[~2012-03-04  4:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 17:39 [PATCH 0/4] Postinst trigger improvements for images Otavio Salvador
2012-03-03 17:39 ` [PATCH 1/4] run-postinsts: fix opkg data path Otavio Salvador
2012-03-03 17:39 ` [PATCH 2/4] image.bbclass: fix rootfs generation without package management tools Otavio Salvador
2012-03-03 17:39 ` [PATCH 3/4] rootfs_rpm.bbclass: rename postinst trigger script Otavio Salvador
2012-03-04  4:31   ` Richard Purdie [this message]
2012-03-05 11:46     ` Otavio Salvador
2012-03-03 17:39 ` [PATCH 4/4] opkg: " Otavio Salvador
2012-03-03 17:54 ` [PATCH 0/4] Postinst trigger improvements for images Otavio Salvador

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=1330835499.3949.18.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 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.