megatron source not packaged in the 3.1.9 tar ball

[HinTak]

Was looking for megatron, and found that it isn't in the 3.1.9 source tar ball from sourceforge. What's going on?

[HinTak]

nor in 3.1.7 or 3.1.8 tar balls.

[HinTak]

found the commit, but without explanation:

commit 6aa1be64b3f4b7b10f85d9aeb4518be1ed95e3ce
Author: Frank Lahm <[email protected]>
Date:   Wed Dec 1 10:34:07 2010 +0100

    Remove megatron from tarball

[HinTak]

Argh, I see, megatron has bit-rotten and no longer build. I guess this needs to be an "un-bitrotting" megatron and update it to current code issue then.

[slowfranklin]

On Tue, Jul 19, 2016 at 03:54:54PM -0700, HinTak wrote:

Was looking for megatron, and found that it isn't in the 3.1.9 source tar ball from sourceforge. What's going on?

was removed in 2010 in commit 6aa1be64b3f4b7b10f85d9aeb4518be1ed95e3ce iirc because there where some serious issues with the code.

Cheerio! -slow

[rdmark]

I want to look into what it would take to de-bitrot megatron in netatalk4.

This was brought up as a request from the community recently, again: https://www.emaculation.com/forum/viewtopic.php?t=12545

A brief experiment revealed that:

• AppleSingle support in libatalk was removed between v2 and v3. This would have to be revived.
• The internal representation of AppleDouble was changed significantly at the same time, so megatron would have to be refactored quite a bit.
• MacBinary and BinHex routines were easy to get compiling again, but whether they work when executed is another question.

[HinTak]

Old binhex and max binary archives are still available in some archive places, for testing.