Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
On 14/06/10 21:05, Pierre Schmitz wrote: On Mon, 14 Jun 2010 00:58:36 +0200, Dominic Reich wrote: "Ivan S. Freitas" wrote: [...] This one I think would be helpful: 5) clean cache with -Sc (or Scc) Oh yes, this one took me some time on pacman -h (with the right switch -S) to get it :) And what about at least one nested usage like: sudo pacman -Rcsn $(pacman -Qqdt) Please, please, nothing with -Rc in it...
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
On Mon, 14 Jun 2010 00:58:36 +0200, Dominic Reich wrote: > "Ivan S. Freitas" wrote: > >> > [...] >> >> This one I think would be helpful: >> 5) clean cache with -Sc (or Scc) >> > > Oh yes, this one took me some time on > pacman -h (with the right switch -S) to get it :) And what about at least one nested usage like: sudo pacman -Rcsn $(pacman -Qqdt) -- Pierre Schmitz, https://users.archlinux.de/~pierre
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
"Ivan S. Freitas" wrote: > > [...] > > This one I think would be helpful: > 5) clean cache with -Sc (or Scc) > Oh yes, this one took me some time on pacman -h (with the right switch -S) to get it :) signature.asc Description: PGP signature
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
> Uhm actually I would place -Ss before -U, because it's almost required for -S > 1) search with -Ss > 2) install with -S > 3) upgrade with -Syu > 4) install AUR package with makepkg -si (or makepkg -s + pacman -U but > I dont use that much) This one I think would be helpful: 5) clean cache with -Sc (or Scc) -- == Ivan Sichmann Freitas Engenharia de Computação 2009 UNICAMP http://identi.ca/ivansichmann Grupo Pró Software Livre UNICAMP - GPSL ==
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
On Sun, Jun 13, 2010 at 4:36 PM, Thomas Bächler wrote: > Am 13.06.2010 16:21, schrieb Xavier Chantry: >> Anyway I have nothing against your proposal, I think it's fine, and >> it's not my call anyway. > > I actually like it a lot, too. > >> There is another question : if we want to extend these EXAMPLES >> section with more stuff from >> http://wiki.archlinux.org/index.php/Pacman (and maybe >> http://wiki.archlinux.org/index.php/Pacman_Tips ?), should we put >> everything in the same man page, or make separate pages ? > > I think we should not have more than 5 examples there, and only very > typical ones, such that a newcomer would pick them up first. > > You want people to know -Syu, -S, and -U first. > Uhm actually I would place -Ss before -U, because it's almost required for -S 1) search with -Ss 2) install with -S 3) upgrade with -Syu 4) install AUR package with makepkg -si (or makepkg -s + pacman -U but I dont use that much) Let's remove all other operations and options which are completely useless :)
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
Am 13.06.2010 16:21, schrieb Xavier Chantry: > Anyway I have nothing against your proposal, I think it's fine, and > it's not my call anyway. I actually like it a lot, too. > There is another question : if we want to extend these EXAMPLES > section with more stuff from > http://wiki.archlinux.org/index.php/Pacman (and maybe > http://wiki.archlinux.org/index.php/Pacman_Tips ?), should we put > everything in the same man page, or make separate pages ? I think we should not have more than 5 examples there, and only very typical ones, such that a newcomer would pick them up first. You want people to know -Syu, -S, and -U first. signature.asc Description: OpenPGP digital signature
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
On Sun, Jun 13, 2010 at 3:44 PM, Nico Schottelius wrote: > > Seems --inline to git send-email wasn't the right then :-/ > Ah well, maybe it's just gmail that does not support these inline mails. But if you don't use any arguments, it should work fine by default. >> +Examples >> + >> + >> +pacman -Syu:: >> + Update package list and upgrade all packages afterwards. >> + >> >> Yeah this is typically the important commands that are not obvious >> when just quickly browsing the man page. >> But as I said, it's already covered in the wiki : >> http://wiki.archlinux.org/index.php/Pacman#Upgrading_packages > > Understood. I'm probably stopping my effort right here, if it's > agreed that the wiki is the primary documentation for pacman. > > I'm probably thinking in different context than the typical archlinux-dev, > for me it's important software can be re-used at other places and thus > I don't think putting "how to get used to tool x" information into a > distribution wiki is a great idea. > > But again, it may be that my thinking way is not compatible to what > you prefer here. > Well we try to keep pacman/makepkg as general as possible and avoid distrib specific bits. So it can be re-used on other systems. But the project is still developed by ArchLinux developers for ArchLinux and all resources are hosted on archlinux.org All resources on archlinux.org are available from any systems, fortunately the web is standard enough for that :) Anyway I have nothing against your proposal, I think it's fine, and it's not my call anyway. There is another question : if we want to extend these EXAMPLES section with more stuff from http://wiki.archlinux.org/index.php/Pacman (and maybe http://wiki.archlinux.org/index.php/Pacman_Tips ?), should we put everything in the same man page, or make separate pages ?
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
Xavier Chantry [Sun, Jun 13, 2010 at 03:36:08PM +0200]: > On Sun, Jun 13, 2010 at 3:28 PM, Nico Schottelius > wrote: > > > > Signed-off-by: Nico Schottelius > > --- > > doc/pacman.8.txt | 10 ++ > > 1 files changed, 10 insertions(+), 0 deletions(-) > > > > > > Not inline, but ok, I will just copy/paste below :) Seems --inline to git send-email wasn't the right then :-/ > +Examples > + > + > +pacman -Syu:: > + Update package list and upgrade all packages afterwards. > + > > Yeah this is typically the important commands that are not obvious > when just quickly browsing the man page. > But as I said, it's already covered in the wiki : > http://wiki.archlinux.org/index.php/Pacman#Upgrading_packages Understood. I'm probably stopping my effort right here, if it's agreed that the wiki is the primary documentation for pacman. I'm probably thinking in different context than the typical archlinux-dev, for me it's important software can be re-used at other places and thus I don't think putting "how to get used to tool x" information into a distribution wiki is a great idea. But again, it may be that my thinking way is not compatible to what you prefer here. > +pacman -U <'path'>:: > + Install package found in the specified file. > + > > This one looks like the abstract description we already have, just shorter : >-U, --upgrade >Upgrade or add package(s) to the system and install the > required dependencies from sync repos. >Either a URL or file path can be specified. This is a > “remove-then-add” process. See Upgrade >Options below; also see Handling Config Files for an > explanation on how pacman takes care of >config files. It is indeed. But if I want to find out "how to install a package from a file", I will go to the examples section instead of reading the whole manpage at first. Nico -- New PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0 Please resign, if you signed 9885188C or 8D0E27A4. Currently moving *.schottelius.org to http://www.nico.schottelius.org/ ... pgpxkd1lhUl3I.pgp Description: PGP signature
Re: [pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
On Sun, Jun 13, 2010 at 3:28 PM, Nico Schottelius wrote: > > Signed-off-by: Nico Schottelius > --- > doc/pacman.8.txt | 10 ++ > 1 files changed, 10 insertions(+), 0 deletions(-) > > Not inline, but ok, I will just copy/paste below :) diff --git a/doc/pacman.8.txt b/doc/pacman.8.txt index 3d14a42..3175ba5 100644 --- a/doc/pacman.8.txt +++ b/doc/pacman.8.txt @@ -415,6 +415,16 @@ original=X, current=Y, new=Z:: necessary changes into the original file. +Examples + + +pacman -Syu:: + Update package list and upgrade all packages afterwards. + Yeah this is typically the important commands that are not obvious when just quickly browsing the man page. But as I said, it's already covered in the wiki : http://wiki.archlinux.org/index.php/Pacman#Upgrading_packages +pacman -U <'path'>:: + Install package found in the specified file. + This one looks like the abstract description we already have, just shorter : -U, --upgrade Upgrade or add package(s) to the system and install the required dependencies from sync repos. Either a URL or file path can be specified. This is a “remove-then-add” process. See Upgrade Options below; also see Handling Config Files for an explanation on how pacman takes care of config files.
[pacman-dev] [PATCH 1/2] add two entries to pacman manpage examples section
Signed-off-by: Nico Schottelius --- doc/pacman.8.txt | 10 ++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/doc/pacman.8.txt b/doc/pacman.8.txt index 3d14a42..3175ba5 100644 --- a/doc/pacman.8.txt +++ b/doc/pacman.8.txt @@ -415,6 +415,16 @@ original=X, current=Y, new=Z:: necessary changes into the original file. +Examples + + +pacman -Syu:: + Update package list and upgrade all packages afterwards. + +pacman -U <'path'>:: + Install package found in the specified file. + + Configuration - See linkman:pacman.conf[5] for more details on configuring pacman using the
