Re: Is pkg quarterly really needed?

[krad]

quarterly does seem very cautious, maybe a monthly might be a good
alternative. I can understand people being hesitant about latest though. I
guess these are not the people who ask though. Maybe the real answer though
is to have a specific repo for that port for the bleeding edge people  much
like launchpad on ubuntu. It might get complicated though for big
dependency trees though.


On 18 April 2017 at 14:54, qjail1  wrote:

> I maintain a port and I have users complaining that the pkg system takes
> many months before the updated version of my port shows up in the pkg
> system.
>
> My response is I tell them to change a line in their /etc/pkg/FreeBSD.conf
> file
> from url: "pkg+http://pkg.Freebsd.org/${ABI}/quarterly;,
> to   url: "pkg+http://pkg.Freebsd.org/${ABI}/latest;,
>
> The old pkg system never had this quarterly update cycle and I see no
> reason to have it now when its so easy to over ride the default.
>
> Why not just change the default to "latest" and save on all the overhead
> of the quarterly cycle?
> ___
> freebsd-questi...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe
> @freebsd.org"
>
___
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: miniupnpd not inserting pf rules

[krad]

cool i was tired so couldnt make the last step, i can confirm removing the
WITH makes the patch get applied



On 12 December 2013 14:34, Volodymyr Kostyrko c.kw...@gmail.com wrote:

 11.12.2013 17:00, krad wrote:

 I have being having some trouble/fun with miniupnpd, in that it didnt seem
 to be inserting the rules into pf ( pfctl -sr -a miniupnpd
 ). The rdr rules are inserted fine just not the firewall rules at the
 rules
 anchor. I think I have traced the problem down to the port build itself. I
 have tested and reproduced it on a clean system on both 9.2 and 10 64bit
 intel builds, but I would be good to have a sanity check make sure i have
 not missed something before I raise a pr/bug report to the maintainer.


 The problem lies with the extra_patch that isnt applied even if the
 dialogue option is checked. Manually specifying it in the environment
 doesn't work either

 ..if ${PORT_OPTIONS:MWITH_PF_ENABLE_FILTER_RULES}
 EXTRA_PATCHES=  ${PATCHDIR}/pf_enable_filter_rules.patch


 Man you are awesome! I had installed this one and thought there was some
 compatibility problems so I just thrashed it.

 In the above example please remove 'WITH_' portion and try to recheck. If
 this will clear things for you - fire up a pr with a patch.

 --
 Sphinx of black quartz, judge my vow.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: HEADS UP: ports/ and 10.0-CURRENT

[krad]

On 27 September 2011 10:18, Anton Shterenlikht me...@bristol.ac.uk wrote:

 On Tue, Sep 27, 2011 at 10:28:49AM +0200, O. Hartmann wrote:
  On 09/27/11 08:35, h h wrote:
  Kevin Obermankob6...@gmail.com  writes:
  
  On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovetta...@freebsd.org  wrote:
  
  With the advent of the conversion of HEAD to 10.0-CURRENT and, as to
 be
  expected, ports/ is going to be essentially unusable for a while.
  
  The issue stems from configure scripts (to choose something completely
  at random) assuming that FreeBSD would never jump to a double-digit
  major version number, and as such, various regexps for freebsd1*
 (ie:
  FreeBSD 1.1.x) are now matching freebsd10.
  [...]
  
  aDe,
  
  Could an entry to this effect be added to UPDATING (with a matching
  entry when ports/ is unbroken).
  
  Also mention a workaround, e.g.
  
 $ export UNAME_r='9.9-BLAH'
 
 
  Now I understand why some OS vendors have choosen the latin 10 'X' for
  their tenth version of their operating system ...

 At least there will be a long rest after
 the move to 10 is complete.. until FreeBSD 100.

 --
 Anton Shterenlikht
 Room 2.6, Queen's Building
 Mech Eng Dept
 Bristol University
 University Walk, Bristol BS8 1TR, UK
 Tel: +44 (0)117 331 5944
 Fax: +44 (0)117 929 4423
 ___
 freebsd-curr...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



we can leave that to our grand children to figure out though 8)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org