On 30 November 2010 09:31, PyroPeter wrote:

Hello AUR users!

I borrowed an arduino recently and found the *arduino*-part of the AUR to be very messy. Here are my findings:

## arduino64-updated [1] Outdated for ages, the copy of a copy of the arduino-PKGBUILD. Can be deleted.

## arduino64 [2] and arduino [3] The difference is difficult to find, the descriptions do not help in any way. arduino depends on avrdude, while arduino64 includes an outdated, but patched avrdude from the Arduino-project.

I wrote an architecture-independent PKGBUILD that could replace arduino and an adapted one that includes the patched avrdude. It could replace arduino64.

I am not sure about the naming of the two new packages, but I think it would make sense to call the package with included avrdude "arduino", because the Arduino SDK includes avrdude by default. The other one could be called "arduino_unpatched". (I am using an underscore here to distinguish it from the "mainname-modulename" notation used by arduino-onewire (which is an add-on for arduino)

tl,dr: arduino64 can be deleted, I would like arduino to be orphaned.

## arduino-pyro [4] I uploaded my new PKGBUILD for the arduino-without-avrdude package under this name to get feedback. It can be deleted.

Regards, PyroPeter

[1] arduino64-updated https://aur.archlinux.org/packages.php?ID=32041 [2] arduino64 https://aur.archlinux.org/packages.php?ID=24053 [3] arduino https://aur.archlinux.org/packages.php?ID=8388 [4] arduino-pyro https://aur.archlinux.org/packages.php?ID=43902

Wow. The last time I used my Duemilanove, there were no such issues. Probably because the package used the internal avrdude. Anyway, +1. Call the patched arduino 'arduino-syslibs' with the description including "(uses system avrdude)".

On 11/30/2010 02:56 AM, Ray Rashif wrote:

Wow. The last time I used my Duemilanove, there were no such issues. Probably because the package used the internal avrdude.

I also use a Duemillanove, but I had to press the reset button every time I uploaded a sketch. Using an avrdude from their SVN solved the problem.

Anyway, +1. Call the patched arduino 'arduino-syslibs' with the description including "(uses system avrdude)".

As I found your description hard to understand, I used a different one: "Arduino SDK (depends on external avrdude and librxtx)" The description of my arduino PKGBUILD would then be: "Arduino SDK (includes patched avrdude and librxtx)" -- freenode/pyropeter "12:50 - Ich drücke Return."

On 1 December 2010 02:53, PyroPeter wrote:

On 11/30/2010 03:03 AM, Ray Rashif wrote:

...

On 30 November 2010 09:56, Ray Rashif  wrote:

...

Wow. The last time I used my Duemilanove, there were no such issues. Probably because the package used the internal avrdude.

Anyway, +1. Call the patched arduino 'arduino-syslibs' with the description including "(uses system avrdude)".

Sorry, forgot to mention:

Ask the arduino maintainer to incorporate your changes. It will not be disowned unless you've sent him an e-mail without any response.

His last action (comment/update) concerning the package was at the 15th of September, and there were loads of bug reports since then. I also posted a link to this thread in the comments of arduino and arduino64.

But this all should not hinder you from deleting arduino-pyro and arduino64-updated.

If there's no response by the end of this week we'll orphan it, so keep a look out. Thanks!

On 5 December 2010 23:46, PyroPeter wrote:

On 11/30/2010 11:18 PM, Ray Rashif wrote:

...

On 1 December 2010 02:53, PyroPeter  wrote:

...

On 11/30/2010 03:03 AM, Ray Rashif wrote:

...

On 30 November 2010 09:56, Ray Rashif    wrote:

...

Wow. The last time I used my Duemilanove, there were no such issues. Probably because the package used the internal avrdude.

Anyway, +1. Call the patched arduino 'arduino-syslibs' with the description including "(uses system avrdude)".

Sorry, forgot to mention:

Ask the arduino maintainer to incorporate your changes. It will not be disowned unless you've sent him an e-mail without any response.

His last action (comment/update) concerning the package was at the 15th of September, and there were loads of bug reports since then. I also posted a link to this thread in the comments of arduino and arduino64.

But this all should not hinder you from deleting arduino-pyro and arduino64-updated.

If there's no response by the end of this week we'll orphan it, so keep a look out. Thanks!

There is still no response, could you orphan/delete the packages now?

Orphaned arduino. What is there to remove again?

Thanks!

The packages to delete are as follows:

[1] arduino64-updated https://aur.archlinux.org/packages.php?ID=32041    outdated and useless

[2] arduino64 https://aur.archlinux.org/packages.php?ID=24053    will be replaced by the new arduino package

[3] arduino-pyro https://aur.archlinux.org/packages.php?ID=43902    replaced by arduino-syslibs

-- freenode/pyropeter                          "12:50 - Ich drücke Return."

Thank you for your work on Arduino! I deleted all of these. Lukas