Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-09-04 Thread Eric Gallager
Does it have to parallel selfupdate? diagnose works perfectly well
by itself without the self in front of it...

On 8/26/14, Craig Treleaven ctrelea...@macports.org wrote:
 On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote:
 
 However, I am not too happy with naming the command 'port doctor'. Many
 other commands used with port(1) are verbs, but using this as a verb
 carries the wrong message.
 
 I know where the naming comes from, but there is no need to match any
 other terminology and we should rather define our own coherent names.
 
 My proposal would be to rename this to 'port selfcheck' instead.
 
 I second the proposal. Selfcheck is a bit awkward, but it does parallel
 selfupdate nicely.
 
 Anything would be better than doctor, which is transparently
 derivative.
 
 'port selfexam' ?
 'port sefldiagnose' ?
 
 Just kidding, but they play on the medical theme...
 
 Craig
 
 ___
 macports-dev mailing list
 macports-dev@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-dev
 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-09-04 Thread Lawrence Velázquez
On Sep 4, 2014, at 5:07 PM, Eric Gallager eg...@gwmail.gwu.edu wrote:

 Does it have to parallel selfupdate? diagnose works perfectly well
 by itself without the self in front of it...

Of course it doesn't *have* to. But most of the port(1) verbs operate on ports 
and port names, whereas selfupdate operates on the MacPorts installation 
itself. So it would make sense to have a selfcheck that checks on the 
MacPorts environment itself, as a whole.

(I know, rev-upgrade and sync [and probably others] don't really operate on 
ports per se. It's a rough guideline.)

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-09-04 Thread Ian Wadham

On 05/09/2014, at 9:59 AM, Lawrence Velázquez wrote:

 On Sep 4, 2014, at 5:07 PM, Eric Gallager eg...@gwmail.gwu.edu wrote:
 
 Does it have to parallel selfupdate? diagnose works perfectly well
 by itself without the self in front of it...
 
 Of course it doesn't *have* to. But most of the port(1) verbs operate on 
 ports and port names, whereas selfupdate operates on the MacPorts 
 installation itself. So it would make sense to have a selfcheck that checks 
 on the MacPorts environment itself, as a whole.

So why not checkself?  Cheers, Ian W.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-09-04 Thread Lawrence Velázquez
On Sep 4, 2014, at 8:04 PM, Ian Wadham iandw...@gmail.com wrote:

 So why not checkself?  Cheers, Ian W.

Because it's not updateself, it's selfupdate.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-09-04 Thread Ian Wadham
On 05/09/2014, at 10:20 AM, Lawrence Velázquez wrote:

 On Sep 4, 2014, at 8:04 PM, Ian Wadham iandw...@gmail.com wrote:
 
 So why not checkself?  Cheers, Ian W.
 
 Because it's not updateself, it's selfupdate.

Well, I was also going to suggest updateself… : -)  the logic being that 
port
commands usually follow the sequence port do-something to-something,
but I realise selfupdate is deeply entrenched…

I suggested checkself because someone, IIRC, did not want to have to type
as far as the u if they required selfupdate.

Cheers, Ian W.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-08-26 Thread Lawrence Velázquez
On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote:

 However, I am not too happy with naming the command 'port doctor'. Many
 other commands used with port(1) are verbs, but using this as a verb
 carries the wrong message.
 
 I know where the naming comes from, but there is no need to match any
 other terminology and we should rather define our own coherent names.
 
 My proposal would be to rename this to 'port selfcheck' instead.

I second the proposal. Selfcheck is a bit awkward, but it does parallel 
selfupdate nicely.

Anything would be better than doctor, which is transparently derivative.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-08-26 Thread Bradley Giesbrecht

On Aug 26, 2014, at 4:54 PM, Lawrence Velázquez lar...@macports.org wrote:

 On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote:
 
 However, I am not too happy with naming the command 'port doctor'. Many
 other commands used with port(1) are verbs, but using this as a verb
 carries the wrong message.
 
 I know where the naming comes from, but there is no need to match any
 other terminology and we should rather define our own coherent names.
 
 My proposal would be to rename this to 'port selfcheck' instead.
 
 I second the proposal. Selfcheck is a bit awkward, but it does parallel 
 selfupdate nicely.
 
 Anything would be better than doctor, which is transparently derivative.

+1 port selfcheck

alt:
port maintenance


Regards,
Bradley Giesbrecht (pixilla)



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Configuration and environment check command (was: Re: [124047] trunk/base)

2014-08-26 Thread Craig Treleaven
 On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote:
 
 However, I am not too happy with naming the command 'port doctor'. Many
 other commands used with port(1) are verbs, but using this as a verb
 carries the wrong message.
 
 I know where the naming comes from, but there is no need to match any
 other terminology and we should rather define our own coherent names.
 
 My proposal would be to rename this to 'port selfcheck' instead.
 
 I second the proposal. Selfcheck is a bit awkward, but it does parallel 
 selfupdate nicely.
 
 Anything would be better than doctor, which is transparently derivative.

'port selfexam' ?
'port sefldiagnose' ?

Just kidding, but they play on the medical theme...

Craig

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev