From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCHv4] dosfstools: version bump: 3.0.28 -> 4.1
Date: Thu, 4 May 2017 17:28:15 +0200 [thread overview]
Message-ID: <20170504152815.aqodyta572glcbud@pengutronix.de> (raw)
In-Reply-To: <20170501080001.nbo7pddfqe7vnisz@pengutronix.de>
On Mon, May 01, 2017 at 10:00:01AM +0200, Robert Schwebel wrote:
> On Sun, Apr 30, 2017 at 11:45:27AM +0200, Robert Schwebel wrote:
> > -# ----------------------------------------------------------------------------
> > -# Install
> > -# ----------------------------------------------------------------------------
> > -
> > -DOSFSTOOLS_INSTALL_OPT := \
> > - $(DOSFSTOOLS_MAKE_OPT) \
> > - install
> > +DOSFSTOOLS_CONF_TOOL := autoconf
> > +DOSFSTOOLS_CONF_OPT = \
> > + $(CROSS_AUTOCONF_USR) \
> > + --disable-compat-symlinks \
>
> One more question: genimage defaults to mkdosfs, but can be overwritten
> in the config or commandline. Shall we continue to provide this name?
That would be best. There is no common name for the old and new versions,
so we can't realy 'fix' genimage. And making sure, this is set everywhere
is a pain.
Michael
--
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 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-05-04 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:44 [ptxdist] [PATCH] " Robert Schwebel
2017-04-27 5:31 ` [ptxdist] [PATCHv2] " Robert Schwebel
2017-04-27 7:43 ` [ptxdist] [PATCH 1/2] " Robert Schwebel
2017-04-28 12:38 ` Michael Olbrich
2017-04-30 9:45 ` [ptxdist] [PATCHv4] " Robert Schwebel
2017-05-01 8:00 ` Robert Schwebel
2017-05-04 15:28 ` Michael Olbrich [this message]
2017-05-07 8:17 ` [ptxdist] [PATCHv5] " Robert Schwebel
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=20170504152815.aqodyta572glcbud@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox