Re: Improvement to port games/ioquake3
> > I think this port has no maintainer so I have no idea who to ping to have > > this committed :) > Most important is to upload the patch to bugs.freebsd.org > so that it does not get lost in the mail flood 8-} Please post > the PR# here, I can work on it. No problem! Here's the PR link: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239180 Thanks! -Greg ___ 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"
Improvement to port games/ioquake3
The port games/ioquake3-server can be used to build a dedicated server for Quake 3 and derivative games. However, it doesn't come with an rc script to launch at system boot or on demand. This makes it a bit tricky to run the dedicated server. This port is a "slave port" that depends on the master port games/ioquake to actually retrieve the source and build everything. I have modified the master port so it now builds and installs an rc script to launch when configured to build the server. In addition, there is a sample .cfg file to start a LAN server which can be modified by the end user, but provides a sane starting point for running the game. I think this port has no maintainer so I have no idea who to ping to have this committed :) games_ioquake3.patch Description: Binary data ___ 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: graphics/php*-gd requires X11 by default
Never mind! I just saw that this was fixed in October for php73-gd. Need to update my PHP version. On Thu, May 16, 2019 at 8:54 PM Greg Kennedy wrote: > I'm raising this again as the last time I tried to check with the port > maintainer, he had not made the change, and wasn't available to do so. > > Can someone change the default config for graphics/php72-gd from X11=on to > X11=off? > > It will save a large number of dependencies on X11, at the cost of not > supporting this (very rarely used) image format. > > On Sat, Sep 15, 2018 at 12:14 PM Greg Kennedy > wrote: > >> I sent an email to the maintainer of these ports (t...@freebsd.org) a few >> days ago, but didn't hear back - so I thought I'd raise the same question >> to the mailing list instead. >> >> --- >> >> Hey there! I was wondering something about the php-gd ports >> (specifically 7.2 but earlier as well). Looking at the config options >> I see this: >> >> X11=on: Enable XPM support >> >> With this option enabled php-gd can read XPixMap images, but in turn >> this pulls in a host of additional X11 dependencies. That's an awful >> lot for (usually) headless servers, especially for an image format >> that is (relatively) unused. I don't mind the option being there but >> because it is defaulted to "on", that means official FreeBSD packages >> are built with this support and all the dependencies. On my system I >> have to manually build this one port just to turn off the option. >> >> Would it be possible to modify the defaults for this port so that >> X11=off by default? Or, why is the default to "on"? (I have a guess, >> that this respects WITHOUT_X11 in /etc/make.conf, but that's useless >> for pre-built binary packages) >> >> -Greg >> > ___ 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: graphics/php*-gd requires X11 by default
I'm raising this again as the last time I tried to check with the port maintainer, he had not made the change, and wasn't available to do so. Can someone change the default config for graphics/php72-gd from X11=on to X11=off? It will save a large number of dependencies on X11, at the cost of not supporting this (very rarely used) image format. On Sat, Sep 15, 2018 at 12:14 PM Greg Kennedy wrote: > I sent an email to the maintainer of these ports (t...@freebsd.org) a few > days ago, but didn't hear back - so I thought I'd raise the same question > to the mailing list instead. > > --- > > Hey there! I was wondering something about the php-gd ports > (specifically 7.2 but earlier as well). Looking at the config options > I see this: > > X11=on: Enable XPM support > > With this option enabled php-gd can read XPixMap images, but in turn > this pulls in a host of additional X11 dependencies. That's an awful > lot for (usually) headless servers, especially for an image format > that is (relatively) unused. I don't mind the option being there but > because it is defaulted to "on", that means official FreeBSD packages > are built with this support and all the dependencies. On my system I > have to manually build this one port just to turn off the option. > > Would it be possible to modify the defaults for this port so that > X11=off by default? Or, why is the default to "on"? (I have a guess, > that this respects WITHOUT_X11 in /etc/make.conf, but that's useless > for pre-built binary packages) > > -Greg > ___ 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"
graphics/php*-gd requires X11 by default
FYI - I received an email from the maintainer of this port - he will resolve this later. Thanks all. ___ 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"
graphics/php*-gd requires X11 by default
I sent an email to the maintainer of these ports (t...@freebsd.org) a few days ago, but didn't hear back - so I thought I'd raise the same question to the mailing list instead. --- Hey there! I was wondering something about the php-gd ports (specifically 7.2 but earlier as well). Looking at the config options I see this: X11=on: Enable XPM support With this option enabled php-gd can read XPixMap images, but in turn this pulls in a host of additional X11 dependencies. That's an awful lot for (usually) headless servers, especially for an image format that is (relatively) unused. I don't mind the option being there but because it is defaulted to "on", that means official FreeBSD packages are built with this support and all the dependencies. On my system I have to manually build this one port just to turn off the option. Would it be possible to modify the defaults for this port so that X11=off by default? Or, why is the default to "on"? (I have a guess, that this respects WITHOUT_X11 in /etc/make.conf, but that's useless for pre-built binary packages) -Greg ___ 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: search.cpan.org is going away (replaced by MetaCPAN)
Thanks, looks like we are all set then! On Wed, May 30, 2018 at 2:10 PM, Adam Weinberger wrote: > On Wed, May 30, 2018 at 12:05 PM James E Keenan wrote: >> >> On 05/30/2018 01:53 PM, Greg Kennedy wrote: >> > Found this news item today relating to Perl: >> > https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html >> > >> > In short, search.cpan.org is being retired on June 25, with the >> > replacement MetaCPAN website to take its place. At that time they >> > will transparently redirect all URL requests to comparable MetaCPAN >> > pages. >> > >> > FreeBSD porting style usually requires that the URL for Perl modules >> > (in pkg-descr) be set to something like... >> > >> > # >> > WWW: http://search.cpan.org/dist/CPAN-Testers-Common-Client/ >> > # >> > >> > While these links will (theoretically) continue working, we should >> > think about a mass find-replace in all "*/p5-*/pkg-descr" URL fields >> > to point to new MetaCPAN URLs. Also, the Porter's Handbook / portlint >> > / etc would need to be updated to recommend using MetaCPAN URLs >> > instead of the existing search.cpan.org links. >> > >> > I didn't see any other discussions on this in the past couple months >> > of the mailinglist archive so I thought I'd raise the issue here :) >> > >> > -Greg >> > >> >> Gret, thank you for calling attention to this. >> >> My hunch is that once search.cpan.org has been retired, we should take a >> sample of the URL fields in the pkg-descr field and verify the links >> they actually resolve to (as distinct from what they are currently >> *expected* to resolve to). At that point, a mass find-replace becomes >> feasible and testable. >> >> Thank you very much. >> Jim Keenan > > Sunpoet already took care of this a few days ago. > > https://svnweb.freebsd.org/ports?view=revision=470993 > > # Adam > > > -- > Adam Weinberger > ad...@adamw.org > https://www.adamw.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"
How long does a new port sit in the Bugs queue?
I created a new port for a Perl library I'm using, and then added an entry for it to freebsd-bugs. This was back on April 24th. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227751 My addition has been sitting in the queue in "New" status since then. I'm in no rush to get it added, but I am curious about how long I can expect new ports to sit in the queue before being acted on. ___ 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"
FreeBSD Port: gifsicle-1.90
Two issues with this port. * There is a new version of this upstream, gifsicle 1.91. * The default config for gifsicle is to include X11 (graphics) support. With this option enabled, you get an additional application "/bin/gifview", which simply lets you view a GIF file in X. This also pulls in a number of x11 dependencies. And, because this is the default FreeBSD config, it causes the package to be built dependent on X. libX11: 1.6.5,1 xproto: 7.0.31 libxcb: 1.12_2 libXdmcp: 1.1.2 libXau: 1.0.8_3 libpthread-stubs: 0.4 kbproto: 1.0.7 Most users DO NOT need this feature: gifsicle is primarily intended for use on servers as a means to lossless-optimize GIF images and save bandwidth. End users who need a gif viewer will almost certainly never use gifview provided by gifsicle, and instead simply use a web browser, or other image viewer. I suggest that the port Makefile be modified so that OPTIONS_DEFAULT is empty instead of containing X11. ___ 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"