On Mon, Jul 15, 2013 at 7:57 AM, Mark Felder wrote:
> On Mon, Jul 15, 2013, at 8:44, RW wrote:
> >
> > Is that really correct? I would expect the deinstall to be done after
> > the build has completed successfully.
> >
>
> That might not be accurate with a current portmaster, but we used to
> hav
On Mon, Jul 15, 2013, at 8:44, RW wrote:
>
> Is that really correct? I would expect the deinstall to be done after
> the build has completed successfully.
>
That might not be accurate with a current portmaster, but we used to
have that happen all too frequently. I just checked the plist and it ha
Walter Hurry wrote:
> On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote:
>
> > As long as this behavior only happens during pkg installs and never with
> > ports, I'm OK. The worst is when a coworker forgets that the mysql port
> > stops the daemon and my coworker upgrades with portmaster... t
On Mon, Jul 15, 2013 at 01:46:03PM +, Walter Hurry wrote:
> On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote:
>
> > As long as this behavior only happens during pkg installs and never with
> > ports, I'm OK. The worst is when a coworker forgets that the mysql port
> > stops the daemon and
On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote:
> As long as this behavior only happens during pkg installs and never with
> ports, I'm OK. The worst is when a coworker forgets that the mysql port
> stops the daemon and my coworker upgrades with portmaster... the daemon
> is off the entire
On Mon, 15 Jul 2013 08:34:05 -0500
Mark Felder wrote:
> On Sun, Jul 14, 2013, at 14:49, Garrett Wollman wrote:
> >
> > Strongly agreed -- and it's what other operating systems do, either
> > by policy or by convention.
> >
>
> As long as this behavior only happens during pkg installs and never
>
On Sun, Jul 14, 2013, at 14:49, Garrett Wollman wrote:
>
> Strongly agreed -- and it's what other operating systems do, either by
> policy or by convention.
>
As long as this behavior only happens during pkg installs and never with
ports, I'm OK. The worst is when a coworker forgets that the mysql
In article <20130714191725.ga30...@stack.nl>, jil...@stack.nl writes:
>Apart from the annoyance of the restarts, automatic stopping and
>starting is probably the best policy for having things "just work". Some
>daemons will crash or otherwise stop being useful when their files have
>been deleted o
On Sun, Jul 14, 2013 at 05:52:37PM +0200, Ian FREISLICH wrote:
> I have to ask if there's a standard for the way ports should handle
> their daemons when the port is uninstalled.
> I've encountered 3 varients of ports behaviour on uninstall:
> 1. Do nothing
> 2. Stop the daemon
> 3. Ask if the da
On Sun, Jul 14, 2013 at 10:52 AM, Ian FREISLICH wrote:
> Hi
>
> I have to ask if there's a standard for the way ports should handle
> their daemons when the port is uninstalled.
>
> I've encountered 3 varients of ports behaviour on uninstall:
>
> 1. Do nothing
> 2. Stop the daemon
> 3. Ask if the
Hi
I have to ask if there's a standard for the way ports should handle
their daemons when the port is uninstalled.
I've encountered 3 varients of ports behaviour on uninstall:
1. Do nothing
2. Stop the daemon
3. Ask if the daemon should be stopped
#1 closely followed by #3 are the least irritat
11 matches
Mail list logo
