All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Strange file names
Date: Tue, 27 Mar 2012 13:37:19 -0500	[thread overview]
Message-ID: <1332873439.20140.22.camel@elmorro> (raw)
In-Reply-To: <20120327182201.96C5E2002FF@gemini.denx.de>

On Tue, 2012-03-27 at 20:22 +0200, Wolfgang Denk wrote:
> Dear Tom Zanussi,
> 
> In message <1332870781.20140.12.camel@elmorro> you wrote:
> >
> > > Arghhh... This is totally broken. Do not do this.
> > 
> > Why do you say so - they're legal filenames and useful for this purpose?
> 
> Not anything that is legal (in the sense that it stretches the
> technical possibilities to the limit) actually makes sense.
> 
> Yes, Unix allows nearly arbitrary file names.  Yes, it is technically
> possible to store the source code of a program or a script in a file
> name.  The fact that nobody does this should make you think if this is
> a clever approach that nobody else could figure out, or if it is just
> plain ......
> 

Yeah, as I mentioned, the motivation was that it seemed the most
straightforward thing to do, notwithstanding the ugliness of the file
names.

> Please consider the mental welfare of the people who have to maintain
> that code after you, who have to type file names like "{{ if
> kernel_choice == "linux-yocto-rt_3.2": }} linux-yocto-rt_3.2.bbappend".
> 

Believe me, I did consider it, since I was the one who had to time them
in in the first place. ;-).

And I have to agree, it is a pain to edit them, mainly because of the
need for quotes - actually I finally resorted to using Nautilus which
made it much easier.

In the end, I balanced that against the fact that it would be very few
people editing these files very rarely (once a release basically), and
decided to do it anyway.

> Even standard commands like "ls" produce output that make my toe nails
> roll up:
> 
> $ ls scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/
> files
> {{ if kernel_choice == "linux-yocto_3.0": }} linux-yocto_3.0.bbappend
> {{ if kernel_choice == "linux-yocto_3.2": }} linux-yocto_3.2.bbappend
> {{ if kernel_choice == "linux-yocto-rt_3.0": }} linux-yocto-rt_3.0.bbappend
> {{ if kernel_choice == "linux-yocto-rt_3.2": }} linux-yocto-rt_3.2.bbappend
> kernel-list.noinstall
> $
> 
> PLEASE do not to this!
> 

If everyone really hates this, I'm perfectly happy with getting rid of
it - it's supposed to be a usability tool after all, and I definitely
don't want to be doing the opposite...

Tom

> Best regards,
> 
> Wolfgang Denk
> 




  reply	other threads:[~2012-03-27 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 14:40 Strange file names Gary Thomas
2012-03-27 14:52 ` Tom Zanussi
2012-03-27 17:43   ` Wolfgang Denk
2012-03-27 17:53     ` Tom Zanussi
2012-03-27 18:22       ` Wolfgang Denk
2012-03-27 18:37         ` Tom Zanussi [this message]
2012-03-29  8:54   ` Detlev Zundel
2012-03-29 14:09     ` Tom Zanussi
     [not found]       ` <m2ty172y60.fsf@lamuella.denx.de>
2012-03-29 16:22         ` Tom Zanussi
2012-03-29 16:22       ` Detlev Zundel

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=1332873439.20140.22.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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.