On 13:24 Thu 18 Dec 2008, Michal Marek wrote:
Brandon Philips napsal(a):
osc co openSUSE:Factory attr cd openSUSE:Factory/attr quilt setup attr.spec cd attr-2.4.39/ ./configure make strace getfattr/getfattr /
Here is a snip from that strace:
open("/home/philips/projects/openSUSE/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) ... Instead of taking on the pain of fixing ld and all of the tools and scripts to generate and understand slash escaped colon characters we could stop using colon as a separator in build service project names.
Another, rather cheap solution, would be an option in the osc client to replace the colon with a dash or underscore or something (and let the user decide what to do when there is a conflict).
If that is the fix then it must be on by default. This problem is subtle and confusing and I don't want other people wasting time figuring it out. We should do the least suprising thing by default: using paths free of special characters.
Because it's really only in osc checkouts where the colon causes problems.
I am not convinced that this is the only place this is causing problems. One example are the repo URLs where the colon characters are used as seperators for directories and there is server magic needed to translate from unslashed to slashed versions... http://download.opensuse.org/repositories/Virtualization:OpenVZ:kernel-2.6.2... directs to http://download.opensuse.org/repositories/Virtualization:/OpenVZ:/kernel-2.6... Are we going to add more server magic to translate from the dashed version of osc too? e.g. http://download.opensuse.org/repositories/Virtualization-OpenVZ-kernel-2.6.2... We can fix osc to do name translation but then all of the other tools should do name translation too... seems like a lot of ongoing work for not a lot of gain. Cheers, Brandon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org