Re: click packages and long symbol names

This looks awesome to me.  I have three small comments.

1. Click's build process already depends on Perl, so what about a 
ruby-to-perl conversion?

2. Rather than the "shortersym" stuff, probably it'd be better to 
implement this as happening on every object.

THANKS!
I'll look at both of these thigns.
Eddie

On 9/19/11 9:45 PM, Cliff Frey wrote:
> I was curious about the issues with maximum symbol length.  This was
> discussed in Eddie's commit b3030b5ac9d1260c6f6a2cd3964114bbbfbd5298.
>
> Here is maybe the very beginning of a fix for the issue, however this
> doesn't actually work for me yet (I'm getting an unknown symbol in sample.ko
> even though that symbol is in my click.ko).  Obviously this code is filled
> with hacks and is not ready yet, but if anyone is actively trying to get
> click packages to work on normal distribution kernels, this is a start.
>
> https://github.com/clifffrey/click/commits/fix-modversions
>
> Cliff
> _______________________________________________
> click mailing list
> [email protected]
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click