pkg_add vs portmaster

[Reid Linnemann]

On Sun, Dec 11, 2011 at 10:09 PM, Mage <mage at mage.hu> wrote:
>        Hello,
>
> why is that
>
> "pkg_add -r x11/kde4" could not install kde4 (404 not found) but "portmaster
> -P x11/kde4" did, however
> "portmaster -P xorg" didn't install xorg (it just reinstalled some modules)
> then "pkg_add -r xorg" installed it.
>
> I am a bit confused with these.
>
> I was reading this:
> http://freebsd.kde.org/
> and this:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-install.html
>
> First I installed kde4 then xorg. My ports are up to date.
>
>        Mage
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"

I think what you're running into here is a difference in semantics
between the pkg_* tools and the ports tools. When using pkg_add -r,
you do not need to specify the category. pkg_add will determine the
proper objformat and release to fetch from ftp, so in this case
"pkg_add -r xorg" will work just fine.

When you use portmaster, it's the opposite. You do need to tell it
'x11/xorg' so it knows you want a specific port in /usr/ports instead
of a glob pattern of an existing port in /var/db/pkg - see this in the
SYNOPSIS section of the man page portmaster(8)

...
     portmaster [Common Flags] full name of port directory in /var/db/pkg
     portmaster [Common Flags] full path to /usr/ports/foo/bar
     portmaster [Common Flags] glob pattern of directories from /var/db/pkg
...

Does that make more sense?