Using outside values in a Portfile tcl

[Gerben Wierda]

Agreed, but then using other strings such as ‘macportshost’ instead of ‘host’ would make it a lot easier to find where they have been used so you know what to change. Host domain and tld are so generic it makes it more difficult to discern what has been the result of basic config.

Gerben Wierda
Chess and the Art of Enterprise Architecture
Mastering ArchiMate
Architecture for Real Enterprises at InfoWorld
On Slippery Ice at EAPJ

On 21 Sep 2019, at 02:45, Steven Smith <steve.t.smith at gmail.com> wrote:

> > obviously, my system isn’t called host.domain.tld or the relayhost mymailrelay.tld.
> 
> Please refer to `port notes mail-server`:
> 
> “Users must reconfigure this installation for their own system, network, and security model specifics by editing all necessary files and checking file permissions.”
> 
> A deployed mail server will require many changes to the example working configuration provided in the mail-server port: TLS, DKIM, DNS, SPF, DMARC, possibly a mail relay, and more. Use the MacPorts configuration as a working basis to start from and edit the configuration for your own deployment. Users must reconfigure the mail-server installation for their own system, network, and security model specifics by editing all necessary files and checking file permissions. 
> 
> Also, these settings are changes in mail-server’s post-activate block to use the current network settings of the installation. See: https://github.com/macports/macports-ports/blob/022f7da78c0cbab9492c60680569cf0483f2e48f/mail/mail-server/Portfile#L328-L342
> 
> Bottom line: don’t waste time trying to coerce a Portfile to automatically configure your deployed mail server when there’s a zillion other settings you’ll have to take care of yourself anyway.
> 
>> On Sep 20, 2019, at 11:37, Gerben Wierda <gerben.wierda at rna.nl> wrote:
>> 
>> The mail-server Portfile has this in it:
>> 
>> # Network configuration
>> # hard-coded examples
>> set host     		host
>> set domain		domain
>> set tld			tld
>> set fullhost		${host}.${domain}.${tld}
>> set domaintld		${domain}.${tld}
>> set HOST                [string toupper ${host}]
>> set DOMAIN     		[string toupper ${domain}]
>> set TLD        		[string toupper ${tld}]
>> set FULLHOST		[string toupper ${fullhost}]
>> set DOMAINTLD           [string toupper ${domaintld}]
>> set relayhost           mymailrelay.tld
>> 
>> Now,  obviously, my system isn’t called host.domain.tld or the relayhost mymailrelay.tld.
>> 
>> Is there a way I can influence these variables from the ‘outside’, so by using envrionment variables or by providing them in some way with the 'port install’ command?
>> 
>> Gerben Wierda
>> Chess and the Art of Enterprise Architecture
>> Mastering ArchiMate
>> Architecture for Real Enterprises at InfoWorld
>> On Slippery Ice at EAPJ
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20190921/5b154a8a/attachment.html>