[gentoo-user] emerge --sync vs emerge -sync

[gentoo-user] emerge --sync vs emerge -sync

[Charles Marcus]

This may be the ultimate dumb question, but no amount of googling could 
satisfy my ignorance...

Is there any difference? If not, why are the double hyphens almost 
always specified?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync vs emerge -sync

[Antoine]

Charles Marcus wrote:
> This may be the ultimate dumb question, but no amount of googling could 
> satisfy my ignorance...
> 
> Is there any difference? If not, why are the double hyphens almost 
> always specified?
> 
I have another for you, which is what I always use
# emerge sync
:-)
Antoine
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync vs emerge -sync

[Richard Fish]

On 1/18/06, Charles Marcus <cmarcus@media-brokers.com> wrote:
> This may be the ultimate dumb question, but no amount of googling could
> satisfy my ignorance...
>
> Is there any difference? If not, why are the double hyphens almost
> always specified?

-- is the GNU getopt syntax for long options.  For normal GNU programs:

--opt is processed as a single option ("opt")
-opt is processed as 6 options ('o', 'p', and 't').

--sync is correct.  -sync is wrong and generates an error.  "sync"
also works, but only because portage specifically looks for it.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --sync vs emerge -sync

[Richard Fish]

On 1/18/06, Richard Fish <bigfish@asmallpond.org> wrote:
> -opt is processed as 6 options ('o', 'p', and 't').

s/6/3/g

-Richard

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: emerge --sync vs emerge -sync

[Charles Marcus]

Richard Fish wrote:
> On 1/18/06, Charles Marcus <cmarcus@media-brokers.com> wrote:
>> This may be the ultimate dumb question, but no amount of googling could
>> satisfy my ignorance...
>>
>> Is there any difference? If not, why are the double hyphens almost
>> always specified?
> 
> -- is the GNU getopt syntax for long options.  For normal GNU programs:
> 
> --opt is processed as a single option ("opt")
> -opt is processed as 6 options ('o', 'p', and 't').
> 
> --sync is correct.  -sync is wrong and generates an error.

Ahem... not for me it didn't... thats why I asked - wondered if I may 
have hosed anything (can't imagine that such a minor, easy-to-make typo 
would caus ebad things to happen, though).

Thanks for the detailed explanation, though... now I at least know the 
differences.

Now, why did it not generate an error for me, I wonder?

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: emerge --sync vs emerge -sync

[Charles Marcus]

>> -opt is processed as 6 options ('o', 'p', and 't').

> s/6/3/g

eh?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: emerge --sync vs emerge -sync

[Richard Fish]

On 1/19/06, Charles Marcus <cmarcus@media-brokers.com> wrote:
> > --sync is correct.  -sync is wrong and generates an error.
>
> Ahem... not for me it didn't... thats why I asked - wondered if I may

What versions of portage & python (emerge -pv portage python)?

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: emerge --sync vs emerge -sync

[Richard Fish]

On 1/19/06, Charles Marcus <cmarcus@media-brokers.com> wrote:
> >> -opt is processed as 6 options ('o', 'p', and 't').
>
> > s/6/3/g
>
> eh?

It is 'sed' syntax.  In english:

replace all ocurrences of the pattern '6' with the string '3'.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: emerge --sync vs emerge -sync

[Michael A. Smith]

Charles Marcus wrote:
> Richard Fish wrote:
> 
>> On 1/18/06, Charles Marcus <cmarcus@media-brokers.com> wrote:
>>
>>> This may be the ultimate dumb question, but no amount of googling could
>>> satisfy my ignorance...
>>>
>>> Is there any difference? If not, why are the double hyphens almost
>>> always specified?
>>
>>
>> -- is the GNU getopt syntax for long options.  For normal GNU programs:
>>
>> --opt is processed as a single option ("opt")
>> -opt is processed as 6 options ('o', 'p', and 't').
>>
>> --sync is correct.  -sync is wrong and generates an error.
> 
> 
> Ahem... not for me it didn't... thats why I asked - wondered if I may 
> have hosed anything (can't imagine that such a minor, easy-to-make typo 
> would caus ebad things to happen, though).
> 
> Thanks for the detailed explanation, though... now I at least know the 
> differences.
> 
> Now, why did it not generate an error for me, I wonder?

Maybe you're thinking of emerge sync:
$ emerge -sync
!!! Error: -y is an invalid short action or option.
dell src # emerge sync
 >>> starting rsync with rsync://129.21.154.146/gentoo-portage...

emerge sync does the same thing as emerge --sync, but actually it's a 
bad habit to get into, because the default behavior for portage is to 
install its non-flag arguments. The implication is that 'emerge sync' 
should install a package named 'sync'.

Of course, that doesn't happen. emerge (sync|info|metadata|...) all 
don't install packages. If you want to install app-vim/info,  you 
have to fully specify its name: emerge app-vim/info.

But you can never tell when such behavior will change. :-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: emerge --sync vs emerge -sync

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 432 bytes --]

On Thu, 19 Jan 2006 13:39:48 -0500, Michael A. Smith wrote:

> > Now, why did it not generate an error for me, I wonder?
> 
> Maybe you're thinking of emerge sync:
> $ emerge -sync
> !!! Error: -y is an invalid short action or option.

Same here. "emerge -sync" is the same as "emerge -s -y -n -c".


-- 
Neil Bothwick

"A computer is like an Old Testament god, with a lot of rules and no
mercy." -- Joseph Campbell

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]