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 Fri, Nov 21, 2014 at 7:05 AM, Mikhail T. mi+t...@aldan.algebra.com
wrote:
The two examples below strike me as particularly aggressive. Speaking as
someone working for a web-hosting group in a major company, I can tell
authoritatively, that -- had we used FreeBSD over there -- we would've
On 22.11.2014 18:19, Kevin Oberman wrote:
It's not like FreeBSD has a to of choice when the BerkeleyDB folks
have dropped db-4.8.
I don't see a connection... People getting their software from Oracle
may have a point to make with the vendor. I'm talking about those, who
install it via FreeBSD
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 two examples below strike me as particularly aggressive. Speaking as
someone working for a web-hosting group in a major company, I can tell
authoritatively, that -- had we used FreeBSD over there -- we would've
found having to upgrade this way unbearable.
We use Red Hat, which emphasizes
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 October 7 PortMgr wrote:
portname: textproc/sxml
description:Skimpy XML parsing and grafting library for C language
maintainer: po...@freebsd.org
deprecated because:
expiration date:2014-08-31
build errors: none.
overview:
On Tue, Oct 07, 2014 at 10:50:01AM -0400, Mikhail T. wrote:
On October 7 PortMgr wrote:
portname: textproc/sxml
description:Skimpy XML parsing and grafting library for C language
maintainer: po...@freebsd.org
deprecated because:
expiration date:2014-08-31
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 Mon, 21 Jul 2014 08:34:19 GMT
lini...@freebsd.org wrote:
portname: lang/rexx-regutil
description:Implementation of IBM's RexxUtil function library
for Regina
maintainer: b...@eager.cx
deprecated because: Not staged. See
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
After a break for over a month due to connectivity issues and other RL crap, a
followup appears...
On Sunday 13 April 2014 20:36:58 John Marino wrote:
On 4/13/2014 19:52, Matthew Rezny wrote:
On Sunday 13 April 2014 18:16:15 John Marino wrote:
On 4/13/2014 17:46, Matthew Rezny wrote:
On
Hi!
Matthew Rezny wrote:
[...]
If you don't like it, then don't do it, but don't stand in the way of anyone
else that does. Also, cut the crap. If maintainer is ports@, then what that
literally means is the ports community as a whole is maintaining those ports.
If they are not maintained
Before I say anything - tonight is a bottle of wine and a night off... ;-)
Also, I've done the steps of fix, stage, and claim maintership. The issue is
honestly be the maintainer. How can I honestly call myself the maintainer
when I can't actually do anything to the port myself.
If
Hi!
They just need converting to a staged environment? If so if you'd like
to take a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=189880 and
tell me if I did it right and tell me how I can choose something that
no-one is working on I'll crack on with some of them.
I test-build the
Kurt Jaeger wrote:
Hi!
They just need converting to a staged environment? If so if you'd like
to take a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=189880 and
tell me if I did it right and tell me how I can choose something that
no-one is working on I'll crack on with some of
Hi!
I agree that there was a lot of change in the ports tree recently.
But: There is a reason for this: The ports tree has to be cleaner
so that it can provide better automatic processes to the users.
It's not easy, but it's getting there.
I found a presentation which really goes deep into
On Sat, May 24, 2014 at 3:01 PM, Kurt Jaeger li...@opsec.eu wrote:
Hi!
I agree that there was a lot of change in the ports tree recently.
But: There is a reason for this: The ports tree has to be cleaner
so that it can provide better automatic processes to the users.
It's not easy, but
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
or not...
--- On Tue, 4/15/14, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote:
From: Jeffrey Bouquet jeffreybouq...@yahoo.com
Subject: Re: FreeBSD ports which are currently scheduled for deletion
To: ports list freebsd-ports@freebsd.org
Date: Tuesday, April 15, 2014, 6:16 PM
On Sun, 4/13/14, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote:
Subject: Re: FreeBSD ports which are currently scheduled for deletion
To: freebsd-ports@freebsd.org
Date: Sunday, April 13, 2014, 11:45 AM
On 4/13/2014 17:46, Matthew Rezny
On 4/13/2014 07:21, Matthew Rezny wrote:
On 4/9/2014 19:56, Christian Weisgerber wrote:
On 2014-04-08, Tijl Coosemans tijl at coosemans.org wrote:
Then, once it is reasonable to assume that a port is unused it is first
marked deprecated which gives users some time to step forward.
There
On Sunday 13 April 2014 09:20:32 John Marino wrote:
On 4/13/2014 07:21, Matthew Rezny wrote:
On 4/9/2014 19:56, Christian Weisgerber wrote:
On 2014-04-08, Tijl Coosemans tijl at coosemans.org wrote:
Then, once it is reasonable to assume that a port is unused it is first
marked deprecated
On 4/13/2014 17:46, Matthew Rezny wrote:
On this list I see cfv, which I've used for years, marked just because
it's
not maintained. It works great, it needs no changes. You want someone to
bloat it with a useless non-feature to prove people still use it? I see
there's a few other sfv
On Sunday 13 April 2014 18:16:15 John Marino wrote:
On 4/13/2014 17:46, Matthew Rezny wrote:
On this list I see cfv, which I've used for years, marked just because
it's
not maintained. It works great, it needs no changes. You want someone to
bloat it with a useless non-feature to prove
On 4/13/2014 19:52, Matthew Rezny wrote:
On Sunday 13 April 2014 18:16:15 John Marino wrote:
On 4/13/2014 17:46, Matthew Rezny wrote:
On this list I see cfv, which I've used for years, marked just because
it's
not maintained. It works great, it needs no changes. You want someone to
bloat it
On 4/13/2014 17:46, Matthew Rezny
wrote:
On this list I see cfv, which I've used for
years, marked just because
it's
not maintained. It works great, it needs no
changes.
I'm not officially a maintainer on any ports for a few
reasons. I have other
areas where I consider
On 4/9/2014 19:56, Christian Weisgerber wrote:
On 2014-04-08, Tijl Coosemans tijl at coosemans.org wrote:
Then, once it is reasonable to assume that a port is unused it is first
marked deprecated which gives users some time to step forward.
There seems to be the general problem, seen
On Wed, 9 Apr 2014 20:26:09 + (UTC) Christian Weisgerber wrote:
On 2014-04-09, John Marino freebsd.cont...@marino.st wrote:
In the meantime -- it's still a non-problem as long as svn revert works.
svn revert throws away local changes. I don't think that's what
you mean.
In fact, I
Tijl Coosemans:
You can undo the russian part of that commit using:
cd /usr/ports
svn merge -c -348843 russian russian
After consulting the Subversion book, I think
svn cp ^/head/russian/xmms@348842 russian
would be the better way to resurrect a port.
Then remove the russian/xmms line
On Wed, Apr 09, 2014 at 11:28:43AM +0200, John Marino wrote:
On 4/9/2014 11:22, Big Lebowski wrote:
While we are not having any way to measure ports usage (or am I wrong
here?), we're still building packages from ports, and I would hope that we
could get some statistics of pkg usage for
On Wed, Apr 9, 2014 at 12:20 AM, Tijl Coosemans t...@coosemans.org wrote:
On Tue, 08 Apr 2014 13:12:48 -0400 Mikhail T. wrote:
On 08.04.2014 12:55, Tijl Coosemans wrote:
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If
On 4/9/2014 11:22, Big Lebowski wrote:
While we are not having any way to measure ports usage (or am I wrong
here?), we're still building packages from ports, and I would hope that we
could get some statistics of pkg usage for certain packages from official
repositories, could we? This is not
Date: Wed, 9 Apr 2014 11:22:58 +0200
Subject: Re: FreeBSD ports which are currently scheduled for deletion
From: Big Lebowski spankthes...@gmail.com
To: Tijl Coosemans t...@coosemans.org
Cc: Mikhail T. mi+t...@aldan.algebra.com,
freebsd-ports
freebsd-ports@freebsd.org
As a sidenote
On Wed, Apr 9, 2014 at 11:28 AM, John Marino freebsd.cont...@marino.stwrote:
On 4/9/2014 11:22, Big Lebowski wrote:
While we are not having any way to measure ports usage (or am I wrong
here?), we're still building packages from ports, and I would hope that
we
could get some statistics of
On 4/9/2014 13:45, Big Lebowski wrote:
On Wed, Apr 9, 2014 at 11:28 AM, John Marino freebsd.cont...@marino.stwrote:
On 4/9/2014 11:22, Big Lebowski wrote:
While we are not having any way to measure ports usage (or am I wrong
here?), we're still building packages from ports, and I would hope
On 2014-04-08, Tijl Coosemans t...@coosemans.org wrote:
For xmms there's xmms2, audacious and numerous other multimedia players.
XMMS works well for what it does, is lightweight by today's standards,
and has survived most of its sucessors. The only alternative is
Audacious, which has much
On 4/9/2014 19:56, Christian Weisgerber wrote:
On 2014-04-08, Tijl Coosemans t...@coosemans.org wrote:
Then, once it is reasonable to assume that a port is unused it is first
marked deprecated which gives users some time to step forward.
There seems to be the general problem, seen again and
On 4/9/2014 2:09 PM, John Marino wrote:
On 4/9/2014 19:56, Christian Weisgerber wrote:
On 2014-04-08, Tijl Coosemans t...@coosemans.org wrote:
Then, once it is reasonable to assume that a port is unused it is first
marked deprecated which gives users some time to step forward.
There seems
On 2014-04-09, John Marino freebsd.cont...@marino.st wrote:
In the meantime -- it's still a non-problem as long as svn revert works.
svn revert throws away local changes. I don't think that's what
you mean.
In fact, I don't know how to even find (the history of) removed
files with Subversion.
Le mer 9 avr 14 à 22:26:09 +0200, Christian Weisgerber na...@mips.inka.de
écrivait :
In the meantime -- it's still a non-problem as long as svn revert works.
svn revert throws away local changes. I don't think that's what
you mean.
In fact, I don't know how to even find (the history
Hi--
On Apr 9, 2014, at 1:26 PM, Christian Weisgerber na...@mips.inka.de wrote:
In fact, I don't know how to even find (the history of) removed
files with Subversion. For instance, at some point there must have
been a port russian/xmms, but neither svnweb nor svn log show it.
You can see the
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If people are using a port, then I would agree it should be kept
regardless of maintainer status. But that doesn't mean keeping
everything forever as long as it compiles.
Why not? Why not keep everything forever as long as it
On 2014-04-08, Mikhail T. mi+t...@aldan.algebra.com wrote:
The most recent list included not only software for interfacing with old
video-cameras -- various modules for xmms, for example, are on the
chopping block too, for just another example. Why?..
I was wondering about the XMMS modules,
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If people are using a port, then I would agree it should be kept
regardless of maintainer status. But that doesn't mean keeping
everything forever as long as it compiles.
Why
On 08.04.2014 12:55, Tijl Coosemans wrote:
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If people are using a port, then I would agree it should be kept
regardless of maintainer status. But that doesn't mean keeping
On 04/08/14 18:12, Mikhail T. wrote:
On 08.04.2014 12:55, Tijl Coosemans wrote:
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If people are using a port, then I would agree it should be kept
regardless of maintainer status.
On Tue, 08 Apr 2014 13:12:48 -0400 Mikhail T. wrote:
On 08.04.2014 12:55, Tijl Coosemans wrote:
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If people are using a port, then I would agree it should be kept
regardless of
Tijl Coosemans wrote:
For xmms there's xmms2
That's no comparison. Not even fracking close. I for one am very glad that
Christian Weisgerber is having a look at the XMMS-related ports.
AvW
P.S. I do agree with your message as a whole, just not with this
particular example.
--
I'm not
On Tue, Apr 8, 2014 at 3:20 PM, Tijl Coosemans t...@coosemans.org wrote:
On Tue, 08 Apr 2014 13:12:48 -0400 Mikhail T. wrote:
On 08.04.2014 12:55, Tijl Coosemans wrote:
On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:
On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:
If
Once again I am seeing this dreadful list and once again I am wondering... Why
are we removing ports simply for being unmaintained?
Those with build-errors -- Ok, I understand, bit-rot happens. Those with (much)
newer versions available -- sure.
But simply unmaintained -- that does not seem
Mikhail T. mi+t...@aldan.algebra.com writes:
Once again I am seeing this dreadful list and once again I am wondering... Why
are we removing ports simply for being unmaintained?
Those with build-errors -- Ok, I understand, bit-rot happens. Those with
(much)
newer versions available -- sure.
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
Hi;
lini...@freebsd.org writes:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.
portname:
On 8/06/2013 4:42 AM, Joseph Mingrone wrote:
Hi;
lini...@freebsd.org writes:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports
Thanks to this email (omitted, too lengthy) I removed directories sheduled for
deletion which would have halted portmaster's procedures were they to be only
existing with my own files within them...
bsdar
games/pets
and copied portmanager, its .so.'s, and man page for safekeeping (I used it in
On Thu, 2012-06-21 at 21:59 -0500, Mark Linimon wrote:
On Thu, Jun 21, 2012 at 01:24:55PM +0200, Stefan Esser wrote:
Am 21.06.2012 10:29, schrieb lini...@freebsd.org:
portname: audio/gstreamer-plugins-flite
description:Gstreamer flite run-time speech synthesis engine
Am 21.06.2012 10:29, schrieb lini...@freebsd.org:
portname: audio/gstreamer-plugins-flite
description:Gstreamer flite run-time speech synthesis engine
plugin
maintainer: multime...@freebsd.org
status: BROKEN
deprecated because: BROKEN
On Thu, Jun 21, 2012 at 01:24:55PM +0200, Stefan Esser wrote:
Am 21.06.2012 10:29, schrieb lini...@freebsd.org:
portname: audio/gstreamer-plugins-flite
description:Gstreamer flite run-time speech synthesis engine
plugin
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
On 21.03.2012 08:00, M. Linimon wrote:
portname: databases/postgresql-tcltk
description:A TCL interface to the database PostgreSQL, including
a tk GUI
maintainer:pg...@freebsd.org
status: BROKEN
deprecated because: Broken for months with no-one
On 21 Mar 2012 13:08, Mikhail T. mi+t...@aldan.algebra.com wrote:
On 21.03.2012 08:00, M. Linimon wrote:
portname: databases/postgresql-tcltk
description:A TCL interface to the database PostgreSQL, including
a tk GUI
maintainer:pg...@freebsd.org
On 21 Mar 2012 16:12, Chris Rees utis...@gmail.com wrote:
On 21 Mar 2012 13:08, Mikhail T. mi+t...@aldan.algebra.com wrote:
On 21.03.2012 08:00, M. Linimon wrote:
portname: databases/postgresql-tcltk
description:A TCL interface to the database PostgreSQL,
including
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
Doug Barton do...@freebsd.org wrote:
On 02/08/2012 02:12, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a ports-infrastructure problem, rather than a
problem in the vrml2pov port.
No,
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a ports-infrastructure problem, rather than a
problem in the vrml2pov port.
No,
On Wed, 08 Feb 2012 02:12:39 -0800, perryh wrote:
lini...@freebsd.org wrote:
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a
Doug Barton wrote:
On 02/07/2012 17:13, Svyatoslav Lempert wrote:
2012/2/7lini...@freebsd.org:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time to propose a way to fix the problems (such as via a
2012/2/8 Miroslav Lachman 000.f...@quip.cz:
Doug Barton wrote:
On 02/07/2012 17:13, Svyatoslav Lempert wrote:
2012/2/7lini...@freebsd.org:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time 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
2012/2/7 lini...@freebsd.org:
The ports, and the reason and date that they have been scheduled
for removal, are listed below. If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.
portname: lang/php52
lini...@freebsd.org wrote:
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a ports-infrastructure problem, rather than a
problem in
On 02/08/2012 02:12, per...@pluto.rain.com wrote:
lini...@freebsd.org wrote:
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a
Hello.
On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
description:Write SQL functions for PostgreSQL using Perl5
maintainer:p...@freebsd.org
deprecated because: No longer supported by upstream-- upgrade to later
On 02/08/2012 10:10, Chad Perrin wrote:
On Wed, Feb 08, 2012 at 09:41:04AM +0400, Alexander Pyhalov wrote:
Hello.
On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
description:Write SQL functions for PostgreSQL using Perl5
On 8 Feb 2012 06:26, Alexander Pyhalov a...@rsu.ru wrote:
On 02/08/2012 10:10, Chad Perrin wrote:
On Wed, Feb 08, 2012 at 09:41:04AM +0400, Alexander Pyhalov wrote:
Hello.
On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
description:
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
1 - 100 of 176 matches
Mail list logo
