suggestion/feature request for Portfile: assert PortSystem comes first

Ryan Schmidt ryandesign at macports.org
Fri Apr 12 16:58:37 PDT 2013


On Apr 12, 2013, at 09:44, Clemens Lang wrote:
> On Fri, Apr 12, 2013 at 08:33:37AM -0400, Brandon Allbery wrote:
>> This would be somewhat difficult, as before the PortSystem line all
>> the PortFile is is raw Tcl code. It doesn't "know" that it should be
>> warning about commands defined by PortSystem.
> 
> while this is true, we could still define a procedure that gets called
> in Tcl when an unknown variable or prodeduce is accessed and print a
> warning that suggests PortSystem might be missing. Something along the
> line of:
> 
> No such variable: configure.agrs, did you forget add PortSystem?


Or it could be a typo.

Or it could be a command that's only available in trunk and not yet in the released version of MacPorts.

I've never heard of anyone putting a line before the PortSystem line, so I don't think this is the most common way to reach an error message and so I don't think it deserves any special handling by base.




More information about the macports-users mailing list