Ticket #10917 (closed defect: wontfix)
BUG: base-1.320 - port upgrades overwrite prefix.mtree
| Reported by: | cilly@… | Owned by: | darwinports-bugs@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | base | Version: | 1.3.2 |
| Keywords: | Cc: | markd@…, jmpp@… | |
| Port: |
Description
i.e. if you set:
/set type=dir uname=root gname=wheel mode=0755
in /usr/local/etc/ports/prefix.mtree then after port selfupdate it is overwritten.
The option should rather be placed into ports.conf to make it sticky.
Change History
comment:1 Changed 7 years ago by markd@…
- Summary changed from port selfupdated destroys ownership and permission set in: /usr/local/etc/ports/prefix.mtree to BUG: base-1.320 - port selfupdate destroys ownership and permission set in: /opt/local/etc/ports/prefix.mtree
comment:2 Changed 7 years ago by markd@…
- Cc markd@… added
- Summary changed from BUG: base-1.320 - port selfupdate destroys ownership and permission set in: /opt/local/etc/ports/prefix.mtree to BUG: base-1.320 - port selfupdate destroys ownership and permission set in: /usr/local/etc/ports/prefix.mtree
Chosing /usr/local as the installation path will not work properly.
comment:3 Changed 7 years ago by markd@…
- Status changed from new to closed
- Resolution set to invalid
comment:4 Changed 6 years ago by cilly@…
- Status changed from closed to reopened
- Resolution invalid deleted
anyway, port selfupdate should not overwrite settings i.e. prefix.mtree without asking
comment:7 Changed 6 years ago by markd@…
I don't know. It could have been fixed indirectly by other fixes I suppose, so I'm not sure we can tell.
comment:8 Changed 6 years ago by cilly@…
Okay, I will pay attention to it on next upgrade.
But I have still problems with another bug so I can't use port selfupdate atm ( http://trac.macports.org/projects/macports/ticket/12041 ).
comment:9 Changed 6 years ago by markd@…
Next upgrade? Selfupdate automatically bumps MP to the latest 1.442. You should be able to upgrade and tell if that file gets overwritten in 5 seconds.
comment:10 Changed 6 years ago by cilly@…
I have installed 1.442 with configure make while /usr/local is empty earlier this day. So it is already at 1.442, I doubt a selfupdate would do anything since it is already the newest version.
comment:11 Changed 6 years ago by markd@…
- Priority changed from Important to Nice to have
- severity changed from Serious to Normal
- Summary changed from BUG: base-1.320 - port selfupdate destroys ownership and permission set in: /usr/local/etc/ports/prefix.mtree to BUG: base-1.320 - port upgrades overwrite prefix.mtree
Oh I misunderstood. A port *upgrade* overwrites the file. I'm sure that behavior is unchanged. Changing summary line.
comment:12 Changed 6 years ago by nox@…
- Cc changed from markd@macports.org,cilly@cilly.mine.nu to markd@macports.org, cilly@cilly.mine.nu
- Priority changed from Nice to have to Low
- Milestone set to MacPorts base bugs
comment:13 Changed 6 years ago by jmpp@…
- Status changed from reopened to closed
- Resolution set to wontfix
- Milestone MacPorts base bugs deleted
prefix.mtree is not a place where user options should be set, the MacPorts developers are in control of that file and should have all the liberty they need to tweak and update it however necessary. If there are options you wish to make user configurable and respected by reinstallations, then please open tickets for them to be included in the macports.conf file, which is indeed not overwritten when upgrading and where all these things should go.
-jmpp
comment:14 Changed 6 years ago by markd@…
- Cc jmpp@… added; cilly@… removed
Juan, shouldn't the text at the top of prefix.mtree be updated? It could state that it should be touched and also the reference to the README file deleted because it doesn't exist.
comment:15 Changed 6 years ago by jmpp@…
Thanks for the suggestion Mark, implemented in r31289. Will merge it to the release branch later on.
-jmpp