This is the current set of dirs replaced:
'BOARDDIR' => BOARDDIR,
'SOURCEDIR' => SOURCEDIR,
'SUBSDIR' => SUBSDIR,
'ADMINDIR' => ADMINDIR,
'CONTROLLERDIR' => CONTROLLERDIR,
'$avatardir' => $modSettings['avatar_directory'],
'$avatars_dir' => $modSettings['avatar_directory'],
'$themedir' => $settings['default_theme_dir'],
'$imagesdir' => $settings['default_theme_dir'] . '/' . basename($settings['default_images_url']),
'$themes_dir' => BOARDDIR . '/themes',
'LANGUAGEDIR' => $settings['default_theme_dir'] . '/languages',
'$languages_dir' => $settings['default_theme_dir'] . '/languages',
'$smileysdir' => $modSettings['smileys_dir'],
'$smileys_dir' => $modSettings['smileys_dir'],
It's a bit of a mixture and I'd even be tempted to just always use a variable-like scheme (e.g $boarddir, $sourcedir, etc.) or something that is evidently a replacement like '{BOARDDIR}'.
The first page is supposed to show any mod you have on the server, while the second just those that are installed.
But yes, the two pages use exactly the same code (AFAIR).
Of course we could add a droppy somewhere or some other kind of link to show only the installed ones without having to go to another page...
I tend to agree.
I think the subdivision comes from Norv's reorganization of the admin area. I think the idea is/was to give more prominence to the "package server" section and promote it as the main place from which retrieve packages.
Though I see it a bit problematic me too: an entire section doesn't mean make it more prominent, to me it means make it more difficult to use.
In package manager, do we really need the "settings" page? There is only the ftp details and IIRC we do not store that settings anywhere in the db, s it's pretty much useless.
File permissions looks more as a maintenance page rather than a "package manager" one.
Package server can be a section of package manager, maybe with some tabs or anything to handle the different options.