As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
On 08/15/2014 14:16, Kurt Jaeger wrote:
Hi!
Consequently, I have no idea how to set the owner/group on those
directories in stagedir.
As can be seen, with some help I was able to find a solution.
I also changed the patches to shebangfixes 8-}
But: There's a real issue coming up in
Hi!
Consequently, I have no idea how to set the owner/group on those
directories in stagedir.
As can be seen, with some help I was able to find a solution.
I also changed the patches to shebangfixes 8-}
But: There's a real issue coming up in
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
Dennis Glatting, and lo! it spake thus:
do_install in the Makefile does the chown.
Generally you'd want to do something more like using @owner/@group in
plist,
Hi!
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
Dennis Glatting, and lo! it spake thus:
do_install in the Makefile does the chown.
Generally you'd want to do something more like using @owner/@group in
On 2014-08-13 18:37, Dennis Glatting wrote:
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
Dennis Glatting, and lo! it spake thus:
do_install in the Makefile does the chown.
Generally you'd want to do something more
On Wed, 2014-08-13 at 18:43 +0200, Kurt Jaeger wrote:
Hi!
On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
Dennis Glatting, and lo! it spake thus:
do_install in the Makefile does the chown.
Done. Thanks.
On Tue, 2014-08-12 at 06:58 +0200, Kurt Jaeger wrote:
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
Hi!
Done. Thanks.
Found it at:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618
Looks cool!
I'll test it on poudriere, but it's CEST here and I have to get up
early, so it will take probably until tomorrow evening to get to it.
--
p...@opsec.eu+49 171 3101372
On Tue, 2014-08-12 at 21:34 +0200, Kurt Jaeger wrote:
Hi!
Done. Thanks.
Found it at:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618
Looks cool!
I'll test it on poudriere, but it's CEST here and I have to get up
early, so it will take probably until tomorrow evening to
Hi!
I'll test it on poudriere, but it's CEST here and I have to get up
early, so it will take probably until tomorrow evening to get to it.
There is one issue with the ordering of 'add the cacti user/group' and
'using it for a chown', but I do not know the fix right away. Will look
at it
On Wed, 2014-08-13 at 06:17 +0200, Kurt Jaeger wrote:
Hi!
I'll test it on poudriere, but it's CEST here and I have to get up
early, so it will take probably until tomorrow evening to get to it.
There is one issue with the ordering of 'add the cacti user/group' and
'using it for a
On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
Dennis Glatting, and lo! it spake thus:
do_install in the Makefile does the chown.
Generally you'd want to do something more like using @owner/@group in
plist, rather than chown'ing in the stage. Doing that would break
building as
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote:
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
deprecated because: Not
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
deprecated because: Not staged. See
Deleting Cacti would be a problem.
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
deprecated because: Not staged. See
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
deprecated because: Not staged. See
Deleting Cacti would be a problem.
Can you
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote:
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer: po...@freebsd.org
deprecated because: Not
Am 07.08.2014 um 18:07 schrieb Dennis Glatting:
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote:
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer:
On 8/08/2014 2:07 AM, Dennis Glatting wrote:
On Thu, 2014-08-07 at 17:36 +0200, Kurt Jaeger wrote:
Hi!
On Thu, 2014-08-07 at 08:29 +, lini...@freebsd.org wrote:
portname: net-mgmt/cacti
description:Web-driven graphing interface for RRDTool
maintainer:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
On 21 April 2013 11:55, Koichiro IWAO m...@vmeta.jp wrote:
2013-04-21 17:30 に lini...@freebsd.org さんは書きました:
portname: net-im/rubygem-termtter
description:Terminal based Twitter client
maintainer: d...@freebsd.org
deprecated because: Does not work with Ruby 1.9
On 2013-04-21 12:55, Koichiro IWAO wrote:
2013-04-21 17:30 に lini...@freebsd.org さんは書きました:
portname: net-im/rubygem-termtter
description:Terminal based Twitter client
maintainer: d...@freebsd.org
deprecated because: Does not work with Ruby 1.9
expiration date:
I found some problems in your patch.
- probably distinfo is not correct
- net/rubygem-rubytter needs to be updated to 1.5.0 or newer
2013-04-22 3:47 olli hauer wrote:
The patch updates the port to version 2.1.0 (ruby 1.9 is supported
since 1.3.x)
I can't make out why the port was marked as
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
The problem with portsmon not updating its ports tree has now been
solved.
mcl
___
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/12/2011 10:06, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: misc/gtkfind
description: The program to use to have to remember all the
options to find(1)
maintainer: po...@freebsd.org
deprecated because: No more
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
lini...@freebsd.org wrote:
portname: misc/gtkfind
description:The program to use to have to remember all the
options to find(1)
maintainer: po...@freebsd.org
deprecated because: No more public distfiles, no more upstream
expiration date:
On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote:
Chris Rees cr...@freebsd.org wrote:
Also, its last update appears to be in 2003, and it's long dead
s/long dead/in good enough shape to be useful/
Indeed:
Project Activity != Project Health
On 11 December 2011 18:01, Chad Perrin c...@apotheon.net wrote:
On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote:
Chris Rees cr...@freebsd.org wrote:
Also, its last update appears to be in 2003, and it's long dead
s/long dead/in good enough shape to be useful/
On Sun, Dec 11, 2011 at 06:45:48PM +, Chris Rees wrote:
On 11 December 2011 18:01, Chad Perrin c...@apotheon.net wrote:
On Sun, Dec 11, 2011 at 03:07:44AM -0800, per...@pluto.rain.com wrote:
Chris Rees cr...@freebsd.org wrote:
Also, its last update appears to be in 2003, and it's
lini...@freebsd.org wrote:
portname: misc/gtkfind
description:The program to use to have to remember all the options
to find(1)
maintainer: po...@freebsd.org
deprecated because: No more public distfiles, no more upstream
Looking at the Makefile,
On Sat, Dec 10, 2011 at 08:00:05AM -0800, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: misc/gtkfind
description:The program to use to have to remember all the options
to find(1)
maintainer: po...@freebsd.org
deprecated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2011 16:00, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: misc/gtkfind
description: The program to use to have to remember all the options
to find(1)
maintainer: po...@freebsd.org
deprecated because: No more
Chris Rees cr...@freebsd.org wrote:
portname: misc/gtkfind
...
Looking at the Makefile, it appears that this port does not
claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e.
the FreeBSD servers. IOW, it looks as if we _are_ the upstream.
Hm. Are you interested in using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2011 04:07 AM, per...@pluto.rain.com wrote:
Chris Rees cr...@freebsd.org wrote:
portname: misc/gtkfind
...
Looking at the Makefile, it appears that this port does not
claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e.
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
On 21 October 2011 07:31, lini...@freebsd.org wrote:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having
Chris Rees wrote on 22.10.2011 18:34:
On 21 October 2011 07:31,lini...@freebsd.org wrote:
portname: databases/postgresql-plpython
description:A module for using Python to write SQL functions
maintainer: po...@freebsd.org
deprecated because: (error in parsing
Bitrot on the original portsmon, due to be replaced by a new instance.
Feel free to ignore.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
On 8 October 2011 10:53, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: net-mgmt/portmon
deprecated because: No more public distfiles
I was able to fetch it earlier today:
$ ( cd /usr/ports/net-mgmt/portmon make fetch-recursive )
=== Fetching all distfiles
On Sat, Oct 08, 2011 at 10:27:12AM +0100, Chris Rees wrote:
On 8 October 2011 10:53, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: net-mgmt/portmon
deprecated because: No more public distfiles
I was able to fetch it earlier today:
$ ( cd
On 8 Oct 2011 23:29, Baptiste Daroussin b...@freebsd.org wrote:
On Sat, Oct 08, 2011 at 10:27:12AM +0100, Chris Rees wrote:
On 8 October 2011 10:53, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: net-mgmt/portmon
deprecated because: No more public
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
1 - 100 of 171 matches
Mail list logo
