Prevent MacPorts editing .bash_profile over and over again...

[Barry Scott]

> On 30 Jan 2017, at 12:44, Barry Scott <barry at barrys-emacs.org> wrote:
> 
> When I run the postinstall as me it works are intended for my .bash_profile.
> When I run via sudo it looks at root’s file and states tit does not support the
> “sh” shell. I suspect that the environment that postinstall is running in is a
> strange in some way. (I have seen Mac specific oddities when developing
> python based apps like no LANG env var.)
> 
> I will need to debug the postinstall script and to do that I need to be able to
> created the .pkg file.
> 
> I have cloned macport-base and done:
> 
> 	./standard-config
> 	Make
> 
> What is the commands you use to create the .pkg?

I found the sudo port -d pkg MacPorts command. But that does not use my git tree.

Barry

> 
> Barry
> 
>> On 29 Jan 2017, at 17:29, Clemens Lang <cal at macports.org> wrote:
>> 
>> Hi,
>> 
>> On Sun, Jan 29, 2017 at 02:13:12PM +0000, Barry wrote:
>>> I have been using the .pkg to reinstall MacPorts. I guess that does
>>> not check.
>> 
>> It does. Specifically, the check checks what your user's shell is using
>> 
>> /usr/bin/dscl . -read "/Users/${USER}" shell | awk -F'/' '{print $NF}'
>> 
>> Supported shells are bash and tcsh. For bash, the installer then runs
>> 
>> bash -l -c "/usr/bin/printenv PATH" | grep "/opt/local"
>> 
>> to determine whether your configuration needs adjusting. For some reason
>> this fails in the installer, although we haven't been able to figure out
>> why.
>> 
>> If you'd like to help debug this, that would be very welcome. I've tried
>> adding more checks for the 2.4.0 release (like doing nothing if the
>> config file to be changed contains 'MacPorts Installer addition'), but
>> apparently none of them worked properly in your case.
>> 
>> 
>> -- 
>> Clemens
>> 
>