Portmaster vs pkg tools

2014-02-14 Thread Stephen R Guglielmo
Hey list,

Back on the previous pkg_* system, I used portmaster to check my port
integrity and dependencies:

portmaster -y -v --clean-distfiles
portmaster -y -v --check-depends
portmaster -y -v --check-port-dbdir

However, I noticed the new `pkg` command has its own `check` and `clean`
commands.

When I run both on the new pkgng format, it seemed to corrupt a database.
Portmaster said things were installed when they weren't, and pkg threw some
errors about packages. I don't have the exact errors anymore because i
fixed it, but I'm wondering which set of commands would be best to use? I'd
assume the pkg tools themselves, as portmaster is an external program.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: dovecot, init script - is this expected or PR worthy?

2014-02-11 Thread Stephen R Guglielmo
On Tue, Feb 11, 2014 at 12:24 PM, Benjamin Podszun 
benjamin.pods...@gmail.com wrote:

 service dovecot start

 and .. that succeeds always, if dovecot_enable=YES is missing (which
 totally is an error on my part, obviously).

 What I expect though is the typical Can't do that, Dave. Try onestart
 perhaps response - and some exit code that signals failure.



 Is that a (tiny, minor) bug? Should I submit a PR for that? Or is that
 totally irrelevant and people out there would never fall for that anyway..?

 Thanks,
 Ben


Hey,

I can't reproduce this on my system. I typically run the rc.d/ scripts
myself, but I did try using the `service` command as well. It works as
expected: The script returns no output when  dovecot_enable is commented
out or set equal to NO in my /etc/rc.conf.local file, and it does not start
or stop the dovecot processes.

I'm using dovecot 1.2.17 on 10.0-RELEASE. Are you using dovecot 2?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org