The Testing Area :: May Extensions
roberts,
Nice to see you back in the forums..
ke4nt
ke4nt, thanks.
jls and mikshaw, I have found 123 .dsl extensions that do not pass the declobber.sh, i.e, clobber_list > 0. Do I just overwrite all these? Make a new section and ask everyone to test them? Or just post the list and and place the burden on the one who contributed them?
Mesa3D and lighttpd upgrade have been posted!
Thanks mikshaw.
Wow 123... I'm probably guilty for one or more (it's like the extensions are saying to fix these are "as easy as 123").
If it doesn't take much time, it would be faster to post all the declobbered extensions in a new section for testing. Then you could also post the list, and those who contributed them, if they are available, can check theirs -- and have users who want a declobbered version of certain extension(s) to test them as well.
Those are the exact words I had planned to begin my reply =o)
My guess is many extensions are simply tgz'ed directories. I can't imagine any other reason for such a huge number.
I wonder, without actually looking at the declobberer, if it is possible to break extensions by using the script? I'm sure there are at least one or two applications that need specific empty directories at runtime (poor coding, I assume?). Would declobbering those extensions kill them? If not, a batch declobber probably wouldn't be a difficult task. If so, I don't know what else to say except good luck =o(
If any of those 123 were my fault, I'll be not unhappy to fix them up. Otherwise I can honestly say I don't care how you approach the problem, considering the only extensions I use that I didn't build myself were made by people I know did them properly (robert, kent, cbagger, clacker...)
Next Page...
original here.