Re: Macports needs a little marketing ....
> On Nov 16, 2016, at 12:09, Daniel J. Luke wrote: > > On Nov 16, 2016, at 10:16 AM, Mojca Miklavec wrote: >> The only thing that could be done would be a slight delay between >> master and "stable". For example everything that's in master would go >> to "quasi-stable" after a week unless some problems are discovered >> (and then the port would be held back). But this requires extra >> manpower again. Something we lack already. > > I think it would be nicer to just be able to have ports tagged with some > metadata (passes lint, buildbot was able to process, installed by n # of > users who have agreed to send stats back to the project, etc.) > > End users could use the metadata to make the kinds of decisions one might > make for 'stable' vs. 'unstable' stuff elsewhere. > > -- > Daniel J. Luke For some manually added metadata, where the upstream purports to fix a CVE, the CVE number it fixes might be of interest to some, especially if the presence of that field could be used to select upgrades.
MacPorts 2.3.5 has been released
The MacPorts Project is pleased to announce the release of version 2.3.5. This is a bugfix release with small changes only, but the first we cut from our new home at GitHub. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs, there are also package installers available for 10.12, 10.11, 10.10, 10.9, 10.8, 10.7, 10.6, and 10.5 at [2]. These installers and the source tarballs are also available from the corresponding v2.3.5 tag on GitHub [3]. Detached PGP signatures for the disk images and package installers have been made by Joshua Root and the source tarballs have been signed with my key. Both public keys are available on the keyservers and our MacPorts wiki pages [4,5], the fingerprints being: 0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58 0C02 01FF 673F B4AA E6CD 0x670191C05C5C6749: 7500 E6A3 6FA5 83B4 071B B540 6701 91C0 5C5C 6749 Rainer (on behalf of the MacPorts Port Managers) [1] https://github.com/macports/macports-base/blob/v2.3.5/ChangeLog [2] https://www.macports.org/install.php [3] https://github.com/macports/macports-base/releases/tag/v2.3.5 [4] https://trac.macports.org/wiki/jmr [5] https://trac.macports.org/wiki/raimue
Re: MacPorts 2.3.5 has been released
Good work! Now, not to sound critical or anything, but when are we going to see the various comments generated for various builds summarised at the end? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Re: MacPorts 2.3.5 has been released
On Nov 17, 2016, at 16:43, Dave Horsfall wrote: > > Now, not to sound critical or anything, but when are we going to see the > various comments generated for various builds summarised at the end? What do you mean? What builds? What comments? Are you taking about the formatting and content of the buildbot build failure emails? If so, you should look at the existing tickets in the issue tracker or open a new email thread with your concerns. This thread should only be about the release of MacPorts 2.3.5 and any issues specific to that.
Re: MacPorts 2.3.5 has been released
> On Nov 17, 2016, at 6:21 PM, Ryan Schmidt wrote: > >> On Nov 17, 2016, at 16:43, Dave Horsfall wrote: >> >> Now, not to sound critical or anything, but when are we going to see the >> various comments generated for various builds summarised at the end? > > What do you mean? What builds? What comments? I think he means aggregation of port notes. vq
Re: MacPorts 2.3.5 has been released
On Thu, 17 Nov 2016, Ryan Schmidt wrote: > > Now, not to sound critical or anything, but when are we going to see > > the various comments generated for various builds summarised at the > > end? > > What do you mean? What builds? What comments? The comments that appear after some installs (OK, so I used the wrong word - I got no sleep last night), such as switching the version of Python that you want to use by default etc. > Are you taking about the formatting and content of the buildbot build > failure emails? If so, you should look at the existing tickets in the > issue tracker or open a new email thread with your concerns. This thread > should only be about the release of MacPorts 2.3.5 and any issues > specific to that. No, I'm talking about something that was planned for 2.3.4, and got told something like "next version", so it sounds relevant to me... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Re: MacPorts 2.3.5 has been released
On Thu, 17 Nov 2016, Lawrence Velázquez wrote: > > What do you mean? What builds? What comments? > > I think he means aggregation of port notes. Yes, those... I'd forgotten the precise term. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Re: MacPorts 2.3.5 has been released
On Thu, Nov 17, 2016 at 6:30 PM, Dave Horsfall wrote: > No, I'm talking about something that was planned for 2.3.4, and got told > something like "next version", so it sounds relevant to me... > They are planned for 2.4, not any release in the 2.3 series. 2.4 is not yet usable for non-developers. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
