Re: bapt@ back on portmgr
from Matthew Seaman and my previous post: > > But what is happening with synth, supposed to make portupgrade and > > portmaster obsolete? > Synth is still being actively developed but the author is now working > primarily on DFly. There is a new maintainer for the synth port who > will be porting the latest updates to FreeBSD, much like almost any > other piece of software in the ports. > At the moment there is a problem with synth on recent FreeBSD HEAD due > to not having a working ada compiler. This will be solved eventually as > the bugs in various toolchains get worked out. My understanding is that the trouble is related to the change to 64-bit inodes on FreeBSD HEAD. lang/gcc5-aux and gcc6-aux won't build. How are users supposed to know if and when this is fixed? I looked in Makefile for ports-mgmt/synth and lang/gcc6-aux and gcc5-aux, and there was no indication of anything amiss. There ought to be a BROKEN notice in the Makefile to save users from the exercise in frustration. For now, I am not doing anything on FreeBSD HEAD; updating 11.1-PRERELEASE (stable branch) instead. Tom ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bapt@ back on portmgr
Matthew Seaman matthew at FreeBSD.org wrote on Fri Jun 9 13:21:34 UTC 2017 > Synth is still being actively developed but the author is now working > primarily on DFly. There is a new maintainer for the synth port who > will be porting the latest updates to FreeBSD, much like almost any > other piece of software in the ports. > > At the moment there is a problem with synth on recent FreeBSD HEAD due > to not having a working ada compiler. This will be solved eventually as > the bugs in various toolchains get worked out. Just an FYI for those who might not know: It turns out that the ports-mgmt/synth author is also the lang/gcc6-aux (ada) author. Unlike synth itself, gcc6-aux has no FreeBSD maintainer last I looked. This indirectly tends to limit synth updates being effective for head. My guess is that gcc6-aux probably has not needed changes or rebuilds for DragonFly BSD. (DragonFly forked from FreeBSD back in FreeBSD-4.x time frames.) So updates appropriate to FreeBSD's head driven by just upstream activity would not seem likely. === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bapt@ back on portmgr
On 09/06/2017 00:54, Thomas Mueller wrote: > from René Ladan: > >> it is our pleasure to announce that Baptiste Daroussin (bapt@) is >> back on portmgr.> > Is this a new port in the works, or is portmgr a (confusing) > abbreviation for portmanager? No, portmgr is the group of people that administer the ports system, issue ports commit bits and so forth. https://www.freebsd.org/administration.html#t-portmgr > I never used portmanager, but remember from the days of the old > pkg_* tools, before pkgng, some users swore by portmanager. > > Then portmanager was not compatible with pkgng. Maybe it can be revived? portmanager needs work to be made compatible with pkg, and will need on-going work to cope with some upcoming changes like sub-package and flavours. There's nothing stopping anyone stepping up and contributing that work, and if anyone is even toying with the idea I'd encourage them to get stuck in -- even small improvements will soon add up. > But what is happening with synth, supposed to make portupgrade and > portmaster obsolete? Synth is still being actively developed but the author is now working primarily on DFly. There is a new maintainer for the synth port who will be porting the latest updates to FreeBSD, much like almost any other piece of software in the ports. At the moment there is a problem with synth on recent FreeBSD HEAD due to not having a working ada compiler. This will be solved eventually as the bugs in various toolchains get worked out. signature.asc Description: OpenPGP digital signature
Fwd: Re: bapt@ back on portmgr
-- Forwarded message -- From: "Freddie Cash" <fjwc...@gmail.com> Date: Jun 8, 2017 9:57 PM Subject: Re: bapt@ back on portmgr To: "Thomas Mueller" <mueller6...@twc.com> Cc: On Jun 8, 2017 9:54 PM, "Thomas Mueller" <mueller6...@twc.com> wrote: from René Ladan: > it is our pleasure to announce that Baptiste Daroussin (bapt@) is back on portmgr. Is this a new port in the works, or is portmgr a (confusing) abbreviation for portmanager? It's an abbreviation for portmanager, the team that manages the ports tree infrastructure aka port...@freebsd.org Cheers, Freddie ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bapt@ back on portmgr
from René Ladan: > it is our pleasure to announce that Baptiste Daroussin (bapt@) is back on > portmgr. Is this a new port in the works, or is portmgr a (confusing) abbreviation for portmanager? I never used portmanager, but remember from the days of the old pkg_* tools, before pkgng, some users swore by portmanager. Then portmanager was not compatible with pkgng. Maybe it can be revived? But what is happening with synth, supposed to make portupgrade and portmaster obsolete? Tom ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
bapt@ back on portmgr
Hello, it is our pleasure to announce that Baptiste Daroussin (bapt@) is back on portmgr. René (on behalf of portmgr) signature.asc Description: OpenPGP digital signature
