Talk:Pacman/Tips and tricks

From ArchWiki
Jump to: navigation, search

pacman-optimize on SSD

[Moved from Talk:Improve pacman performance -- Alad (talk) 05:05, 16 October 2015 (UTC)]

pacman-optimize only tries to reduce fragmentation of the files right? If that is the case perhaps we should include a note that this probably won't help much on an SSD. —This unsigned comment is by F4hy (talk) 18:27, 29 March 2013‎. Please sign your posts with ~~~~!

pacman-optimize

[Moved from Talk:Improve pacman performance -- Alad (talk) 05:05, 16 October 2015 (UTC)]

Looks like the systemd-timer-pacman-optimize-git package is no longer maintained. [1]

Should the wiki no longer recommend this package? -- I'm guessing it shouldn't.

Also, is pacman-optimize less important than in the past? -- I am genuinely unsure about this.

--Matthew02 (talk) 05:40, 2 March 2015 (UTC)

The maintenance of systemd-timer-pacman-optimize-gitAUR has nothing to do with that of pacman itself, it is packaged separately and even in the AUR. Anyway, I'd keep the section until pacman-optimize is removed from pacman.
The reasons why it is not very important nowadays are improvements in pacman itself (mentioned in the ML post linked above), increased speeds of HDDs and the advent of SSDs.
-- Lahwaacz (talk) 22:18, 2 March 2015 (UTC)

Leading slash

Pacman/Tips_and_tricks#aria2 doesn't work without leading slash, i.e. -d / turning file names to //var/cache/.... The article mentions this, but it doesn't mention why. -- Alad (talk) 05:28, 16 October 2015 (UTC)

You would have to go way back to track this. It seems to have worked without -d / even in 2006: [2], [3]. I guess that simply nobody asked the right question... -- Lahwaacz (talk) 12:30, 16 October 2015 (UTC)
Oops, it does not work without -d /. Then the problem must be on aria's side, which expects a file name for the -o option, which is then catenated with -d into the full path. Assuming that -d defaults to the cwd, /var/cache/ would appear twice in the result. -- Lahwaacz (talk) 12:43, 16 October 2015 (UTC)

comm & LC_COLLATE

What's the problem exactly? The inputs are sorted by sort according to LC_COLLATE, which is expected by comm. The exact value of the variable does not matter, it must only stay the same for both tools (and in these tips it does). -- Lahwaacz (talk) 14:06, 25 March 2016 (UTC)

Either way, grep is simpler than comm + sort, and if later examples want to keep an existing order, grep respects it. -- Alad (talk) 14:29, 25 March 2016 (UTC)
Using grep instead of comm + sort is sort of like shooting a sparrow with a cannon. Combining two tools following the Unix philosophy is certainly simple enough, but on the other hand using grep -Fxf (let alone grep -Fxvf) as an alternative is (IMO very) unintuitive. -- Lahwaacz (talk) 21:23, 25 March 2016 (UTC)
Well, it's hard to argue about philosophy and intuition, so I'll wait on a third opinion to close the matter. :P -- Alad (talk) 22:09, 25 March 2016 (UTC)
I've added a note with [4] so people can decide what they like best. Closing. -- Alad (talk) 17:30, 30 March 2016 (UTC)