On Sun, 2015-10-11 at 12:06 +0100, Ian Campbell wrote:
> [...]
> > There is still an unresolved inconvenience related to Linux
> > distributions arbitrarily renaming the tools when doing sunxi-tools
> > packaging. It would be great if we could have a unification of the
> > tool names just for the sake of ensuring that the documentation and
> > howto guides can be easily used without confusing the users.
> 
> The Debian package (of v1.2-ish) has:
>         install -m0755 usb-boot $(PKG)/usr/bin/sunxi-usb-boot
>         install -m0755 fel $(PKG)/usr/bin/sunxi-fel
>         install -m0755 fexc $(PKG)/usr/bin/sunxi-fexc
>         install -m0755 bootinfo $(PKG)/usr/bin/sunxi-bootinfo
> 
> I'd be happy to put that together as a patch for upstream instead.

If we do want to do this then there's a few choices to make:

Which tools to prefix with "sunxi-" and which to not. I'd be inclined
to prefix most of them except but keep fex2bin bin2fex as they are.

Renaming the source files vs. having the Makefile e.g. build fel.c into
a sunxi-fel binary. Makefile has a mixture of explicit rules and a
implicit (%: %.c) one.

Shall we add an install target to the Makefile or not. If yes then
which tools is useful to add to the install target.

I would rule out having the install target perform the rename, since I
think it is not uncommon for instructions etc to involve running the
tools right out of the build tree, so having those use different names
to what is installed would be v. confusing.

I'd be inclined to:
 * Prefix everything except bin2fex+fex2bin with sunxi-
 * Try doing the rename via Makefile runes to start with but consider
   renaming if the Makefile gets too ugly
 * Add an install rule starting with just the 4 mentioned above. Others
   can be added later.

In the absence of any objections I'll knock up a patch one evening this
week.

Ian.

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to