Excerpts from anonymous's message of Thu Aug 19 03:58:42 -0400 2010: > > uri=URI.encode(uri) ### <--- Added this line in order to encode "special" > characters within the uri. > > This makes sup-add work, it encodes the non-standard characters (like > "%20" for " "). They appear as such in sources.yaml. But this breaks > another part: sup-sync now looks for files containing "%20" instead of > " " on the disk, which obviously don't exist: If you're going to URI encode the source URIs (makes sense if they're truly URIs), you're going to have to URI decode them before use. I'm not sure if this is the best approach, but you should be able to turn what you've done into a working patch by finding the places where sup uses the URIs and using URI.decode(uri) to turn them back into normal strings at the right moment.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel