Re: App::* - what's it for?

2006-04-12 Thread Johan Vromans
Eric Wilhelm [EMAIL PROTECTED] writes: That happens in bin/ as well though, so I think those clashes are necessary. Yes, but they're relatively harmless. If App::FooBar and App:BarBlech both prove an app superapp, then I can choose which one to install. Okay, I cannot install both apps

Re: App::* - what's it for?

2006-04-12 Thread A. Pagaltzis
* Johan Vromans [EMAIL PROTECTED] [2006-04-12 11:10]: Yes, but they're relatively harmless. If App::FooBar and App:BarBlech both prove an app superapp, then I can choose which one to install. Okay, I cannot install both apps simultaneously. But App::SuperApp and App::SuperApp will confuse the

Re: App::* - what's it for?

2006-04-12 Thread A. Pagaltzis
* Daniel T. Staal [EMAIL PROTECTED] [2006-04-12 20:50]: It just seems like bad practice to use meaningful metadata that is *not* necessarily constant (though it often is in practice) as part of a unique identifier. It makes the system less adaptable. org::acmecorp::App::FooBar?