[publican-list] --lang vs --langs

[Bram Vogelaar]

my +1 for this semantic distinction between single and multiple languages options.

This way the option to use is sort of a clue bat to guide you to correctly formulating the command to run.
 
bram

On 11 Jun 2010, at 03:21, Ryan Lerch wrote:

> On Fri, 2010-06-11 at 08:46 +1000, Ruediger Landmann wrote:
>> On 06/11/2010 07:36 AM, Jaromir Hradilek wrote:
>> 
>> Actually, I find this is a valuable semantic distinction for me as a 
>> user as well. Because you can perform some actions on multiple languages 
>> at a time, and some actions on only one language at a time, having to 
>> type the correct option helps me keep these separate in my mind.
>> 
>> If the --lang and --langs options were to be mashed together, we'd 
>> really need an error message for the actions that can only be performed 
>> on one language at a time that says something like "You can only package 
>> one language at a time."
>> 
>> Then of course people might wonder why we have an option called "langs" 
>> that only allows you to perform an action on a single language.
>> 
>> Maybe we should just leave it as it is.
>> 
> 
> I agree,
> 
> the first time i used "publican package" i tried to specify multiple
> langs with "langs=" but it failed. If the commands were mashed together,
> what i tried to do would still fail, as i can only specify one lang when
> building a package. allowing "langs=" to work will only confuse further.
> 
> my 2 cents: keep the distinction between langs= and lang=.
> 
> cheers,
> ryanlerch
> 
> _______________________________________________
> publican-list mailing list
> publican-list at redhat.com
> https://www.redhat.com/mailman/listinfo/publican-list
> Wiki: https://fedorahosted.org/publican