This ticket this fix came from predated the snowleopard_fixes portgroup. You're quite correct - since the portgroup was committed, that would be the proper fix now. -- K
On Fri, Nov 10, 2017 at 5:59 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Oct 19, 2017, at 08:57, Kurt Hindenburg wrote: > > > Kurt Hindenburg (kurthindenburg) pushed a commit to branch master > > in repository macports-ports. > > > > > > https://github.com/macports/macports-ports/commit/ > 7e06fb25e9464ce95d9474b0095c21069bd6d07f > > > > The following commit(s) were added to refs/heads/master by this push: > > > > new 7e06fb2 util-linux: add snowleopardfixes > > > > 7e06fb2 is described below > > > > > > commit 7e06fb25e9464ce95d9474b0095c21069bd6d07f > > > > Author: Kurt Hindenburg <khindenb...@macports.org> > > AuthorDate: Thu Oct 19 09:56:15 2017 -0400 > > > > > > util-linux: add snowleopardfixes > > > > > > > > closes https://trac.macports.org/ticket/54410 > > > > @@ -59,6 +59,11 @@ configure.args --disable-agetty \ > > # When adding new programs, check the .c file for license > > build.target colcrt column look rename rev scriptreplay setsid > > > > +platform darwin 10 { > > + depends_lib-append port:snowleopardfixes > > + configure.ldflags-append -lsnowleopardfixes > > +} > > Why only apply this on Snow Leopard? Aren't earlier systems affected too? > > Why not just include the portgroup which handles the details for you? > >