1. Forum
  2. Usenet
  3. COMP.UNIX.BSD.FREEBSD.MIS

  • elementary browser plugin questions

    From Winston@21:1/5 to All on Sun Nov 22 16:50:41 2020
    My impression is that /usr/ports/www/xpi-* are browser "plugin"s.
    'pkg rquery %n | grep xpi-' is empty, so its repository has none.
    'pkg help' says there's a "pkg plugins" to list plugins, but I
    see nothing special for obtaining or installing plugins.

    * If plugins are installed just like other pkg packages, why have a
    separate pkg command "plugins" to list them, especially if the
    repository has none?

    Using the browser to visit its maker's website to install a plugin
    would seem to be incompatible with pkg tracking what's installed.

    * So what's the standard practice? Build plugins from /usr/ports?
    Does "pkg audit" report security problems with software installed from
    /usr/ports like it does for pre-built packages from its repository?

    Thanks in advance,
    -WBE

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bob Eager@21:1/5 to Winston on Sun Nov 22 22:34:47 2020
    On Sun, 22 Nov 2020 16:50:41 -0500, Winston wrote:

    My impression is that /usr/ports/www/xpi-* are browser "plugin"s. 'pkg
    rquery %n | grep xpi-' is empty, so its repository has none. 'pkg help'
    says there's a "pkg plugins" to list plugins, but I see nothing special
    for obtaining or installing plugins.

    * If plugins are installed just like other pkg packages, why have a
    separate pkg command "plugins" to list them, especially if the
    repository has none?

    I think you are misunderstanding. The pkg command 'plugins' refers to
    plugins for the pkg command itself, e.g.:

    https://forums.freebsd.org/threads/pkg-plugins.65466/

    --
    Using UNIX since v6 (1975)...

    Use the BIG mirror service in the UK:
    http://www.mirrorservice.org

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Winston@21:1/5 to I previously on Sun Nov 22 18:40:08 2020
    I previously asked:
    * If [browser] plugins are installed just like other pkg packages,
    why have a separate pkg command "plugins" to list them, especially
    if the repository has none?

    Bob Eager <news0073@eager.cx> kindly replied:
    I think you are misunderstanding. The pkg command 'plugins' refers to
    plugins for the pkg command itself, e.g.:

    Ah, OK. That makes more sense, in which case you're right, I
    misunderstood. Thanks,
    -WBE

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)