Re: [tuxdroid-user] Including dfu-programmer in tuxsetup

[neimad <ror...@gm...>]

"David Bourgeois" <da...@ja...> writes:

>> What makes it hard for joe user to compile ? Couldn't it be seamlessly
>> integrated in the "tuxup procedure" (neved used it) ?
>
> Well, the feedback we get from the marketing is that a lot of geeks
> whiich  are not programmers think tux is still at the prototype stage.
> Which  somehow is ot wrong neither. I think that the next firmware
> update will be  a good improvement mostly for the energy savings. But
> people are afraid  when they read that the first thing you have to do
> is get the sources of  dfu-programmer, compile it, then upgrade the
> firmware. Then we still don't  have any real end user software with
> polished gui so that also makes them  stay doubtful about the project
> status.

As a first step, could tuxup automatically download, compile and
install dfu-programmer and all necessary tools ? Of course, it won't
help much on Ubuntu, as you point out below...

> Most newbies are using ubuntu so maybe another solution would be to
> maintain a debian/ubuntu dfu-programmer package. I could also do an
> ebuild  for gentoo but I don't think gentoo users will get trouble on
> that side.  On ubuntu, you can't compile dfu-programmer without
> installing a bunch of  developer packages like build-essentials,
> libusb-devel, etc. GCC isn't  installed by default. It took me some
> time to look around the first time I  used ubuntu to get all the
> dependencies necessary to compile. So I guess  some users will really
> benefit from a package. Even worse it seems there's  a debian package
> around which doesn't work, so some people end up there  too.

Oh, I forgot about that. The first time I installed Ubuntu, I was
puzzled and unnerved I couldn't do any programming on it ! You're
right, packages would indeed be the right thing for this distribution.

> Usually when I don't know what to do, I try to do both and check later
> on  what's the best option. We can try to support dfu-programmer as
> packages  for some distributions and also include it in tuxsetup. If
> it already  exists on the system, it's not used, otherwise it tries to
> launch it, use  it if it works or tell the user to compile from
> sources otherwise.

This may work as a first step towards user-friendliness, yes. Anyone
experienced with Debian/Ubuntu packaging ? :-)

	Damien