From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] New package: openvmtools
Date: Wed, 30 Jul 2014 00:51:32 +0200 [thread overview]
Message-ID: <20140729225132.GC5846@free.fr> (raw)
In-Reply-To: <CABbD_XBsgVB7KQPwKoEJDz3JOJ61_2AJO=JtNOWy+yiRqgrTQQ@mail.gmail.com>
Karoly, All,
On 2014-07-30 00:41 +0200, K?roly Kasza spake thusly:
> Thanks for reviewing my patch!
Cheers! ;-)
[--SNIP--]
> > This scripts uses a mix of tabs and spaces to do the indentation; for
> > example, the cases lines ("start)", "stop)"...) are indented with
> > spaces, while the rest is indented with tabs. Please be consistent.
>
> I used dropbear's startup script as a template, and the indentation is
> exactly the same. Also with openssh, exim or ptpd (and possibly some
> others). I think I should not differ from those too much?
OK, I undersand. But those scripts were intially written a loooong time
ago. We prefer that new submissions be a bit more coherent. Eventually,
someone will clean up those old scripts. One day. Maybe... ;-)
> > > +
> > > +exit $?
> >
> > No need to exit epxlicitly, it's implicit from POSIX, that a shell
> > script exits with the error code from the last command. Besides, we do
> > not care at all about the exit status of a startup script.
>
> Although you are right, it's on the end of the dropbear startup script and
> 26 other initscripts in the package/ subdir. I think I should leave this to
> stay consistent with the others as above.
I prefer we introduce sane new scripts. As said above, the others are
really old, and no longer up to nowadays standards...
> > > +OPENVMTOOLS_CONF_OPT = \
> > > + --without-icu \
> > > + --without-x \
> > > + --without-gtk2 \
> > > + --without-gtkmm \
> > > + --without-kernel-modules
> >
> > On a single line. If it is too long, just split it, like:
> >
> > OPENVMTOOLS_CONF_OPT = --without-icu --without-x \
> > --without-gtk2 --without-gtkmm --without-kernel-modules
>
> OK. I though it is more visible.
I agree, but that's not the coding rules. ;-)
> > No --enable-fuse/--disable-fuse options (or the likes)?
>
> Unfortunately not. If the "configure" script finds libfuse, it builds
> vmblock-fuse, else it won't. I experimented with it a bit, and found this
> the most logical solution.
OK, then.
> Thanks again, I'll send a v5 patch soon. Regarding the init script, I can
> use only spaces/tabs, but then this script will differ from the others.
> Should I?
Yes, new scripts should be cleaner and saner than the old ones.
Thanks for your persistence with this patch! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-07-29 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 11:57 [Buildroot] [PATCH v4 1/1] New package: openvmtools Karoly Kasza
2014-07-29 21:15 ` Yann E. MORIN
2014-07-29 22:41 ` Károly Kasza
2014-07-29 22:51 ` Yann E. MORIN [this message]
2014-07-29 23:02 ` Károly Kasza
2014-07-29 21:45 ` Thomas Petazzoni
2014-07-29 22:49 ` Károly Kasza
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=20140729225132.GC5846@free.fr \
--to=yann.morin.1998@free.fr \
--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.