From: Sascha Hauer <s.hauer@pengutronix.de>
To: Johannes Stezenbach <js@sig21.net>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] command: introduce abi version
Date: Mon, 29 Oct 2012 11:31:16 +0100 [thread overview]
Message-ID: <20121029103116.GQ1641@pengutronix.de> (raw)
In-Reply-To: <20121029095604.GA31639@sig21.net>
On Mon, Oct 29, 2012 at 10:56:04AM +0100, Johannes Stezenbach wrote:
> On Mon, Oct 29, 2012 at 09:50:55AM +0100, Sascha Hauer wrote:
> > On Mon, Oct 22, 2012 at 06:07:26PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > This will allow to detect incompatibility between the env abi and the current
> > > barebox one
> ...
> > > +
> > > +#define COMMAND_ABI_VERSION 0
> >
> > Please describe what this is. Something like:
> >
> > /*
> > * This tracks incompatible changes to the barebox command interface.
> > * This number is increased when changes are introduced which will cause
> > * an older environment to no longer work. This could be:
> > *
> > * - changes in commandline options to commands
> > * - renames of commands
> > * - rename of device files
> > *
> > * If you change this value, add a explanation of the actual change to
> > * Documentation/command-abi-changes.txt
> > */
>
> I wonder how this will work in practice. If I use a simple
> /env/bin/init script and someone makes changes to a command
> which isn't used by my /env/bin/init, will it still cause
> my environment to be detected as incompatible?
>
> Maybe it would be a good idea to give the user control
> over when to change COMMAND_ABI_VERSION by putting it into menuconfig?
>
> Either way I guess it means the default environment's init script
> would need to implement automatic update to not lose important settings.
I see the same problems and I am not really happy with introducing an
ABI version.
Also, introducing an ABI version could motivate people to break the ABI just
because it's simple to do so and we have a standard way of doing it.
>
> Bottom line: It's much better to not make incompatible ABI changes _ever_.
Agreed. In case of the change to the mount command this could mean to
preserve the old ABI at least for compatibility. In case of my USB/MMC
disk example this could mean to add links.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-10-29 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:03 [PATCH 0/3] introduce command abi version Jean-Christophe PLAGNIOL-VILLARD
2012-10-22 16:07 ` [PATCH 1/3] command: introduce " Jean-Christophe PLAGNIOL-VILLARD
2012-10-22 16:07 ` [PATCH 2/3] envfs: add command_abi_version support Jean-Christophe PLAGNIOL-VILLARD
2012-10-23 8:59 ` Sascha Hauer
2012-10-23 10:20 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-23 12:56 ` Sascha Hauer
2012-10-23 13:27 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-22 16:07 ` [PATCH 3/3] environment: detect command_abi_version Jean-Christophe PLAGNIOL-VILLARD
2012-10-29 8:50 ` [PATCH 1/3] command: introduce abi version Sascha Hauer
2012-10-29 9:56 ` Johannes Stezenbach
2012-10-29 10:31 ` Sascha Hauer [this message]
2012-10-29 16:05 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-29 17:00 ` Johannes Stezenbach
2012-10-29 18:05 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-23 8:51 ` [PATCH 0/3] introduce command " Sascha Hauer
2012-10-23 10:28 ` Jean-Christophe PLAGNIOL-VILLARD
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=20121029103116.GQ1641@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=js@sig21.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.