-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-11-26 at 17:23 -0200, Luiz Fernando Ranghetti wrote:

maybe:

zypper in -t pattern devel_kernel

Ah! Yes, that's it.

http://en.opensuse.org/Zypper/Usage/11.0#Installing_Packages (other examples)

Hum! The examples should be inside the man page, not outside.

or zypper in --help (look for --type)

which lacks examples. Once I know that I have to specify the package type, yes, I can see it in the help. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkktqEIACgkQtTMYHG2NR9WsegCfbF0JR/76w22HUzFMRd1DfREx DHEAn03oHBzyOwFQ/1knRqa1jQjQ4A6E =qtWF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-11-26 at 18:07 -0200, Luiz Fernando Ranghetti wrote:

...

Hum! The examples should be inside the man page, not outside.

...

or zypper in --help (look for --type)

which lacks examples. Once I know that I have to specify the package type, yes, I can see it in the help.

That's what is supposed to explain with the 'default' in every zypper command (install, upgrade, update, etc):

-t, --type <type> Type of package (%s).\n Default: %s.\n

] NOT_nimrodel:~ # zypper help in ] install (in) [options] ... ] ] Install packages with specified capabilities or RPM files with specified ] location. A capability is NAME[OP<VERSION>], where OP is one of <, <=, ] =, >=, >. It is above where it should tell that the package type has to be specified, and which is the default, not below - IMO: ] Command options: ] -r, --repo Install packages only from the specified ] repository. ] -t, --type <type> Type of package (package, patch, ] pattern, product). ] Default: package. The phrasing is not very fortunate.

Seams that the man page of zypper was remade some weeks ago, I don't remember in which list it was announced...

The current man page, where you look at the command install, does not mention "patterns": ] install (in) [options] ... ] Install or update packages. ] ] The packages can be selected by their name or by a ] capability they provide. ] ] Capability is: NAME, or "NAME[.ARCH][OP<EDITION>]", ] where ARCH is architecture code, OP is <, <=, =, ] >=, or > and EDITION is VERSION[RELEASE]. For ] example: zypper=0.8.82. ] ] The NAME component of a capability is not only a ] package name but any symbol provided by packages: ] /bin/vi, libcurl.so.3, perl(Time::ParseDate). Just ] remember to quote to protect the special characters ] from the shell, for example: zypper\>0.8.10 or zypϖ ] per>0.8.10 ] ] If EDITION is not specified, the newest installable ] version will be installed. This also means that if ] the package is already installed and newer versions ] are available, it will get upgraded to the newest ] installable version. ] ] If ARCH is not specified, or the last dot of the ] capability name string is not followed by known ] architecture, the solver will treat the whole ] string as a capability name. If the ARCH is known, ] the solver will select a package matching that ] architecture and complain if such package cannot be ] found. ] ] Zypper will report packages that it cannot find. ] Further, in interactive mode, zypper proceeds with ] installation of the rest of requested packages, and ] it will abort immediately in noninteractive mode. ] In both cases zypper returns ZYPϖ ] PER_EXIT_INF_CAP_NOT_FOUND after finishing the ] operation. ] ] Zypper is also able to install plain RPM files ] while trying to satisfy their dependencies using ] packages from defined repositories. You can install ] a plain RPM file by specifying its location in the ] install command arguments either as a local path or ] an URI. E.g.: ] ] $ zypper install ~/rpms/foo.rpm ] http://some.site/bar.rpm ] ] Zypper will download the files into its cache ] directory (/var/cache/zypper/RPMS), add this direcϖ ] tory as a temporary plaindir repository and mark ] the respective packages for installation. ] ] In the install command, you can specify also packϖ ] ages you wish to remove in addition to the packages ] you wish to install, by prepending their names by a ] or ~ character. For example: ] ] $ zypper install vim emacs ] $ zypper remove emacs +vim ] ] will both install vim and remove emacs. Note that ] if you choose to use with the first package you ] specify, you need to write before it to prevent ] its interpretation as a command option. ] ] $ zypper install boringgame greatgame greatgameϖ ] manual If you position the cursor in the man page at the "install" command, and you search for the word "pattern", you will see it first appears on the "remove" command, not on the "install" command. I looked for the info on how to install patterns looking on the man page for the "install" command, and then for how to install a pattern searching for the word "pattern" - and after I couldn't find it, I had to ask here. If, on the man page you look for the modifiers of "install", you see: ] t, type <type> ] Type of package (default: package). See the beginϖ ] ning of this subsection for the list of available ] package types. Again, "pattern" is not mentioned. Thus, IMO, the man page is not good enough for a person that doesn't already know how to use zypper. - -- Cheers. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkktuUIACgkQtTMYHG2NR9UqmACfYEe3SBTeaX8Gq/UKCsQerdQB HFYAn3GkntaAl5xxBVUEj97eM4uxmYl2 =WjYZ -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: On Thursday, 2008-11-27 at 11:41 +0100, Jan Kupec wrote:

Carlos E. R. wrote:

...

...

...

which lacks examples. Once I know that I have to specify the package

Examples in the help texts? Hmm.. why not? :O) The only thing against i can think of is the work it takes. You're welcome to help, BTW :O)

Ha! :-) Well... the help text is already largish... I was probably thinking of the man pages. And as a translator that has translated man pages, I can say that I hate translating man pages, I hate the format and not having real easy (non programmesse) writing tools. For a user, the man format is ok, but for a plain writer... ugh. And I can tell you that we sweated translating zypper :-p

...

] Command options: ] -r, --repo Install packages only from the specified ] repository. ] -t, --type <type> Type of package (package, patch, ] pattern, product). ] Default: package.

The phrasing is not very fortunate.

Go ahead and suggest something better.

I don't know, but some lines like: zypper in rpm_package zypper in -t pattern pattern_package at the bottom of the "zypper help in" text would help. Or at the top. Some samples of the possible combinations.

...

If, on the man page you look for the modifiers of "install", you see:

] t, type <type> ] Type of package (default: package). See the beginÖ ] ning of this subsection for the list of available ] package types.

Again, "pattern" is not mentioned.

"See the beginning of this subsection for the list of available package types."

Yeah, I know... once you know what you have to look for. But, if you use the text search facility of "man" to search for "pattern" after going to the section "install", you find nothing in that section. You have to actually read the entire section and digest it before you notice what it means >:-)

...

Thus, IMO, the man page is not good enough for a person that doesn't already know how to use zypper.

I know, we improve it gradually. In fact i plan to work on it in the upcoming days. So thanx for pointing this out :O)

Welcome! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkukl4ACgkQtTMYHG2NR9Us2wCeJlXQ3RXX7ECpQrejZ3fdycAq +hAAnAlm4a9uF8wJw2nVvIjeCc3KfVwg =RE7S -----END PGP SIGNATURE-----