On Fri, 22 May 2009 22:56:33 +0700 Edho P Arief <edhopr...@gmail.com> wrote: > On Fri, May 22, 2009 at 5:53 PM, Thomas Pfaff <tpf...@tp76.info> wrote: > > Trying to add a few packages on my -current system and there's > > some weirdness going on that I believe was not present before: > > > > Script started on Fri May 22 12:34:41 2009 > > $ sudo pkg_add -v samba > > $ sudo pkg_info -I samba > > samba-3.0.34 B B B B SMB and CIFS client and server for UNIX > > samba-3.0.34-ads B B SMB and CIFS client and server for UNIX > > samba-3.0.34-cups B SMB and CIFS client and server for UNIX > > samba-3.0.34-cups-ads SMB and CIFS client and server for UNIX > > samba-3.0.34-cups-ldap SMB and CIFS client and server for UNIX > > samba-3.0.34-ldap B SMB and CIFS client and server for UNIX > > $ sudo pkg_add -v samba-3.0.34 > > parsing samba-3.0.34 > > ^C > > perhaps you meant > > pkg_add -i pkgname >
That enters interactive mode and I'm presented with the correct choices (as listed above) so, sure, that works. Without the -i option, however, pkg_add just terminates. This is on May 18th userland. On another system of mine running February 28th user- land the pkg_add behaviour is different, and as I would expect: Feb28$ sudo pkg_add vim Ambiguous: vim could be vim-7.2.77-gtk2 vim-7.2.77-no_x11 Feb28$ May18$ sudo pkg_add vim May18$ As far as I can tell, both systems are configured the same with respect to the package manager (Feb28 is i386 and May18 is amd64 though).
