All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Remove clean and uninstall targets [was: Re: [PATCH 1/2] Add (Freescale) elftosb host package]
Date: Thu, 15 Mar 2012 22:06:34 +0100	[thread overview]
Message-ID: <201203152206.35139.arnout@mind.be> (raw)
In-Reply-To: <4F607CD9.2080300@lucaceresoli.net>

On Wednesday 14 March 2012 12:11:21 Luca Ceresoli wrote:
> Moreover, many packages do not implement the CLEAN and UNINSTALL targets:
> 
> $ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'|wc -l
> 111
> $ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'| \
>      xargs grep -l '_CLEAN_CMDS'|wc -l
> 51
> $ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'| \
>      xargs grep -l '_UNINSTALL_.*_CMDS'|wc -l
> 73
> 
> meaning that probably they are not so interesting to everybody out there.

 Uninstall doesn't really work, as Thomas pointed out, so I'm all for 
removing it.

 For the clean target I can imagine a use case, but it's not very
convincing.  Say you're preparing a package patch the painful way 
(i.e. save a copy the source tree, modify the files of the source tree, 
and if all is well run a diff).  Then you may have some modifications 
which are not detected by make (e.g. when you're actually editing the 
Makefile).  So you want to run a make clean.  make foo-dirclean is not
possible because then you loose your changes.  This is where a clean
target could be useful.

 However, it's such a corner case that I don't think it's important.
And if you're hacking away at a package, you can afford to run
'make -C output/build/foo-0.1 clean' manually.


 Removing the clean and uninstall targets will make tab completion
slightly faster as well :-)


 So let's get rid of them!


 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2012-03-15 21:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 12:52 [Buildroot] [PATCH 0/2] add u-boot.sb file format and elftosb tools Eric Jarrige
2012-03-13 12:52 ` [Buildroot] [PATCH 1/2] Add (Freescale) elftosb host package Eric Jarrige
2012-03-13 15:10   ` Thomas Petazzoni
2012-03-14  0:05   ` Arnout Vandecappelle
2012-03-14  9:41     ` Thomas Petazzoni
2012-03-14 11:11       ` Luca Ceresoli
2012-03-14 11:57         ` Thomas Petazzoni
2012-03-15 21:06         ` Arnout Vandecappelle [this message]
2012-03-15 21:28           ` [Buildroot] Remove clean and uninstall targets [was: Re: [PATCH 1/2] Add (Freescale) elftosb host package] Thomas Petazzoni
2012-03-15 21:32             ` Arnout Vandecappelle
2012-03-13 12:52 ` [Buildroot] [PATCH 2/2] u-boot: add support for u-boot.sb file format Eric Jarrige
2012-03-13 14:17   ` Thomas Petazzoni
2012-03-13 14:52     ` Eric Jarrige
2012-03-13 15:06       ` Thomas Petazzoni
2012-03-13 15:11   ` 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=201203152206.35139.arnout@mind.be \
    --to=arnout@mind.be \
    --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.