Redundant prefix.mtree ... was creating directories for destroot

Juan Manuel Palacios jmpp at macports.org
Mon Nov 12 09:46:26 PST 2007


	Hi Mark!

On Nov 12, 2007, at 12:58 PM, markd at macports.org wrote:

> Juan Manuel Palacios <jmpp at macports.org> writes:
>> $[juan @macbookpro: macports1.0](858/0,1) -> sudo find /opt/local -
>> name macosx.mtree
>> /opt/local/share/macports/resources/port1.0/install/macosx.mtree
>>
>> $[juan @macbookpro: macports1.0](859/0,1) -> sudo find /opt/local -
>> name prefix.mtree
>> /opt/local/etc/macports/prefix.mtree
>> /opt/local/share/macports/resources/port1.0/install/prefix.mtree
>>
>> 	I wonder if we still use the mtree file installed in ${prefix}/etc/
>> macports/ for something? Anyone care to destroot a port after moving
>> it aside and report any findings? (comparing to destrooting after
>> moving the one in /opt/local/share/macports/resources/port1.0/
>> install/ aside would be ideal).
>
> I don't recall anyone ever answering this, though I could be wrong.   
> I am
> cleaning out my doc related email stuff and tried it.  Here are the
> results:
>
> Move ${prefix}/etc/macports/prefix.mtree  ->  Result:  ports  
> destroot fine
> and still pass mtree checks
>
> Move ${prefix}/share/macports/resources/port1.0/install/ 
> prefix.mtree  ->
> Result:  ports fail to destroot with this message:
>
> "mtree: /opt/local/share/macports/resources/port1.0/install/ 
> prefix.mtree:
> No such file or directory"
>
>
> So I suppose we should remove ${prefix}/etc/macports/prefix.mtree  
> since it
> is redundant and not needed anymore?
>
> Mark


	I removed the installation of prefix.mtree from ${prefix}/etc/ 
macports a while ago, but thanks for the confirmation anyhow!

	Regards,....


-jmpp



More information about the macports-dev mailing list