Re: Q about post-extract recent commit breakage
On Dec 4, 2018, at 12:03, Michael Dickens wrote:
> On Tue, Dec 4, 2018, at 2:07 AM, Ryan Schmidt wrote:
>> On Dec 4, 2018, at 01:04, Ryan Schmidt wrote:
>>> On Dec 3, 2018, at 19:35, Michael Dickens wrote:
>>>
Here's the error (just do "sudo port extract cmake-devel"; it results in
this error on every OS I tested, from 10.5 to 10.14):
{{{
Error: Failed to extract cmake-devel: error renaming
"/opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_devel_cmake/cmake-devel/work/cmake-772edffbf0c08fc0a6fcf74fb98545b7afcfee13-772edffbf0c08fc0a6fcf74fb98545b7afcfee13"
to
"/opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_devel_cmake/cmake-devel/work/cmake-772edffbf0c08fc0a6fcf74fb98545b7afcfee13/cmake-772edffbf0c08fc0a6fcf74fb98545b7afcfee13-772edffbf0c08fc0a6fcf74fb98545b7afcfee13":
trying to rename a volume or move a directory into itself
Error: See
/opt/local/var/macports/logs/_opt_sources_MacPorts_ports_github_macports_devel_cmake/cmake-devel/main.log
for details.
}}}
>>>
>>> Ok, that's because cmake-devel does this:
>>>
>>> post-extract {
>>> move ${workpath}/${name}-${commit}-${commit}
>>> ${workpath}/${name}-${commit}
>>> }
>>>
>>> Now that base has been changed, MacPorts has already made a ${worksrcdir}
>>> (in this case ${name}-${commit}) symlink for you. So for compatibility with
>>> both the released version of MacPorts and master, you should ensure it
>>> doesn't already exist before moving it:
>>>
>>> post-extract {
>>> if {![file exists ${worksrcpath}]} {
>>> move ${workpath}/${name}-${commit}-${commit} ${worksrcpath}
>>> }
>>> }
>>>
>>> which is basically what's done in the remaining commit for libao in this PR:
>>>
>>> https://github.com/macports/macports-ports/pull/1760
>>>
>>> After compatibility with the current version of MacPorts is no longer
>>> needed, the entire post-extract block can be removed.
>>
>> Or, more simply and more usually, you should be able to just:
>>
>> worksrcdir${name}-${commit}-${commit}
>>
>> (and again, if desired, remove it once a future version of MacPorts is
>> released).
>
> Or, even more simply, just remove the post-extract all together. I don't
> recall why it's the in the first place, but removing it seems to do the
> trick. Thanks!
That works with the not-yet-released MacPorts master version, but does not work
with the released MacPorts 2.5.4; for that version, you still need to set
worksrcdir manually when it is not the default value. Fixed in
860f9c647f60a33043e8a13dfe688c575faa88cd.
Re: Q about post-extract recent commit breakage
Ah yes; very good! Thanks for that fix; it should be removed with the next MP release, yes? - MLD On Wed, Dec 5, 2018, at 5:05 AM, Ryan Schmidt wrote: > On Dec 4, 2018, at 12:03, Michael Dickens wrote: > > Or, even more simply, just remove the post-extract all together. I don't > > recall why it's the in the first place, but removing it seems to do the > > trick. Thanks! > > That works with the not-yet-released MacPorts master version, but does > not work with the released MacPorts 2.5.4; for that version, you still > need to set worksrcdir manually when it is not the default value. Fixed > in 860f9c647f60a33043e8a13dfe688c575faa88cd.
Re: macports rot
On 03.12.18 17:00, Jonathan Stickel wrote: > I would like to express some concerns about trends I've noticed in the > Macports community. I've been a Macports user and contributor for many > years. I understand the imperfect nature of open-source projects run by > volunteers. Interest and contributions, both by developers and periphery > contributors, waxes and wanes. It seems to me that Macports is waning. > With the move to github, developer and port-maintainer attention to > tickets on trac really dropped off. This was partially made up for by > increased attention and fast turnaround with pull requests. Recently, > even pull requests are languishing. Reasonable fixes are ignored, or, if > problems with the contributions are identified by developers and > maintainers, the problems are pointed out with no effort to provide > constructive input. > > I try to help where and when I can. When something is not working for > me, I try my best to find a fix and contribute a pull request. I also > respond in a reasonable time to tickets and PRs for ports for which I am > maintainer. I think this is quite reasonable and the best I can do > considering my paying job. I know that I do not have enough time to act > as a developer, and so I am not asking for that. Your observation might be right, but maybe this just becomes more visible now on GitHub. Just take a look at the number of open tickets on Trac. There are also many tickets with proposed ports or fixes. However, if the submitter does not have enough interest to follow through, the ticket will just hang there. I feel like many "oldschool" developers already left the platform, because more and more functionality is put behind some wall that only Apple can penetrate. Gatekeeper, signed Kernel Extension, and SIP impose limits on what you can do with macOS, while non-Apple developers do not even get proper logging when APIs become forbidden and blocked. I guess that users coming to macOS now are used to graphical interfaces and do not have a strong background in using the command line. I am sure many are more happy with Homebrew, where they do not even have to use sudo! ;-) Somehow the Homebrew community managed to get their ubiquitous marketing on almost every software project website. Compare this with the MacPorts website, which has not seen any redesign in more than 10 years... Although a good package management system should not need to advertise itself, as every software would be available without users being told where to look – the package manager should be their first choice. > So where is Macports headed? I think the core architecture and systems > of Macports are well built. It just needs a little more attention. How > can we achieve that? Has Homewbrew simply siphoned off too much user and > developer base? I don't know. I would also like to point out that there was also no discussion on the recent thread that we have a problem with the process to on-board new project members... That is one of the most important things that needs to be solved as it affects the whole community. Similarly on the recently failed online meeting and especially the topic of joining the Software Freedom Conservancy or more general to form any kind of legal entity. The project definitely needs more steering. But to be fair and transparent on this, I am personally not able to provide this at the moment. Rainer
Scheduled downtime on Dec 14
Hello, due to maintenance on the network in the data center where our server is hosted, there will be a 20-minute disconnection in the time frame given below. Start: 2018-12-14 03:00:00 UTC End:2018-12-14 05:00:00 UTC (expected) This will mostly affect the website, Trac, and the mailing lists. GitHub can be used as usual, but any WebHook sent from GitHub to Trac during the downtime will fail and will have to be re-triggered manually once the system is online again. Rainer
Re: macports rot
Yeah Rainer, I was surprised that that thread went nowhere. I’m ok with not being ready to be on boarded or needing to learn more, but it’s still been radio silence. The thing is I still am a much bigger fan of this project and community than Homebrew. I’ve been thinking of an idea to compete with Cask. I’m trying to take over things that are no maintainer that I want to use. I’ve been on MacPorts since 10.3 and I don’t want it to die or languish. But I’m not sure exactly what to do. I’m certainly only going to homebrew kicking and screaming. I remember those early nasty advertisements focused on this community. I really want to get more involved, help with tooling, maybe get a Swift MacPorts.framework working. But I have no idea how. If anyone has ideas I’m looking to dive in and I’m on Eastern Time. I’ve asked for commit access and bumped portmgr a few times, but other than that I don’t know exactly how to help. —Mark > Your observation might be right, but maybe this just becomes more > visible now on GitHub. Just take a look at the number of open tickets on > Trac. There are also many tickets with proposed ports or fixes. However, > if the submitter does not have enough interest to follow through, the > ticket will just hang there. > > I feel like many "oldschool" developers already left the platform, > because more and more functionality is put behind some wall that only > Apple can penetrate. Gatekeeper, signed Kernel Extension, and SIP impose > limits on what you can do with macOS, while non-Apple developers do not > even get proper logging when APIs become forbidden and blocked. > > I guess that users coming to macOS now are used to graphical interfaces > and do not have a strong background in using the command line. I am sure > many are more happy with Homebrew, where they do not even have to use > sudo! ;-) > > Somehow the Homebrew community managed to get their ubiquitous marketing > on almost every software project website. Compare this with the MacPorts > website, which has not seen any redesign in more than 10 years... > > Although a good package management system should not need to advertise > itself, as every software would be available without users being told > where to look – the package manager should be their first choice. > > > So where is Macports headed? I think the core architecture and systems > > of Macports are well built. It just needs a little more attention. How > > can we achieve that? Has Homewbrew simply siphoned off too much user and > > developer base? I don't know. > > I would also like to point out that there was also no discussion on the > recent thread that we have a problem with the process to on-board new > project members... That is one of the most important things that needs > to be solved as it affects the whole community. > > Similarly on the recently failed online meeting and especially the topic > of joining the Software Freedom Conservancy or more general to form any > kind of legal entity. > > The project definitely needs more steering. But to be fair and > transparent on this, I am personally not able to provide this at the > moment. > > Rainer > -- Sent from Gmail Mobile on iPhone
