Re: saving a few ports from death

2011-05-01 Thread Doug Barton
On 05/01/2011 00:12, mato wrote: Regarding hosting the files -- one of the goals of the foundation is to provide infrastructure for the project. And this seems like one of the opportunities to do so. Besides, all of the ports mentioned have their distfiles already mirrored on FreeBSD's FTP. I

Re: saving a few ports from death

2011-05-01 Thread mato
Doug Barton wrote: On 04/25/2011 17:28, martinko wrote: Ok, I skimmed through the list of deprecated ports and I identifed the following that I may be using or at least used in past and I could take over their maintenance to save them from death: Generally by the time that a port has deteriora

Re: saving a few ports from death

2011-04-28 Thread Chris Rees
On 27 Apr 2011 21:04, "Mikhail T." wrote: >> cvs's Attic can be easily restored if people take up the slack. I see >> no reason to change this policy > > No, not easily. It requires the CVS tree, which is not automatically installed. What are you on about? Just do an anonymous checkout, like ever

Re: saving a few ports from death

2011-04-27 Thread Doug Barton
On 04/27/2011 13:54, Eitan Adler wrote: Which is a*major* drain of resources. One of the reasons for ceasing the building of packages for broken/completely obsolete is to avoid draining the computer time building said packages. ... and in addition to CPU cycles there is also storage on the doz

Re: saving a few ports from death

2011-04-27 Thread Olli Hauer
On 2011-04-27 17:59, Mikhail T. wrote: > On -10.01.-28163 14:59, Robert Huff wrote: >> It is also possible it is only important to a fairly small >> number ... but to those it is absolutely crucial. > Or the port might become useful/essential/critical to somebody in the > future... > > What i

Re: saving a few ports from death

2011-04-27 Thread Erik Trulsson
On Wed, Apr 27, 2011 at 05:05:57PM -0400, Eitan Adler wrote: > >> apache13 is EOL upstream. We should not have ports for EOL software. > > > > Why not, exactly?.. > > What happens if a security hole or a bug is found? Are we the ones to > fix it? If yes are we to host the patches? Where should the

Re: saving a few ports from death

2011-04-27 Thread Mikhail T.
Eitan, you are entitled to your opinions, but not to your own facts. My factual corrections are inline below. Arguing about opinions and policy is useless until the facts are accepted as such by all participants: On 27.04.2011 16:54, Eitan Adler wrote: The upstream maintainer already called

Re: saving a few ports from death

2011-04-27 Thread Chip Camden
Quoth Ade Lovett on Wednesday, 27 April 2011: > On Apr 27, 2011, at 13:46 , Chip Camden wrote: > > > > Modifying the script that was posted earlier, we can list out all > > installed ports that are currently deprecated, and why: > > Won't work -- need to handle slave ports etc, where the DEPRECAT

Re: saving a few ports from death

2011-04-27 Thread Charlie Kester
On Wed 27 Apr 2011 at 14:05:57 PDT Eitan Adler wrote: apache13 is EOL upstream. We should not have ports for EOL software. Why not, exactly?.. What happens if a security hole or a bug is found? Are we the ones to fix it? No. The rule of caveat emptor should apply. We don't warranty anyth

Re: saving a few ports from death

2011-04-27 Thread Eitan Adler
>> apache13 is EOL upstream. We should not have ports for EOL software. > > Why not, exactly?.. What happens if a security hole or a bug is found? Are we the ones to fix it? If yes are we to host the patches? Where should the bug reports go to - our bug tracker? What if our implementation ceases t

Re: saving a few ports from death

2011-04-27 Thread Mikhail T.
On 27.04.2011 16:47, Wesley Shields wrote: apache13 is EOL upstream. We should not have ports for EOL software. Why not, exactly?.. If upstream says it's dead, who are we to keep it alive? We are a major Operating System project, which maintains ports of third-party applications for the conven

Re: saving a few ports from death

2011-04-27 Thread Eitan Adler
>dougb is anxious to delete apache13 as well instead of simply disowning it... The upstream maintainer already called it "end of life". FreeBSD does not and will not ever take over the development of dead upstream ports (and in this case there is a upstream version) >The same entity(ies), that cu

Re: saving a few ports from death

2011-04-27 Thread Wesley Shields
On Wed, Apr 27, 2011 at 04:03:58PM -0400, Mikhail T. wrote: > On 27.04.2011 14:16, Eitan Adler wrote: > > Then bapt@ marked the ports*deprecated* which does not mean deleted. It > > was a warning that people who were interested should step up and take up > > the work. If after N amount of time n

Re: saving a few ports from death

2011-04-27 Thread Mikhail T.
On 27.04.2011 14:16, Eitan Adler wrote: Then bapt@ marked the ports*deprecated* which does not mean deleted. It was a warning that people who were interested should step up and take up the work. If after N amount of time no one does so they will be individually deleted. The ports I listed -- d

Re: saving a few ports from death

2011-04-27 Thread Ade Lovett
On Apr 27, 2011, at 13:46 , Chip Camden wrote: > > Modifying the script that was posted earlier, we can list out all > installed ports that are currently deprecated, and why: Won't work -- need to handle slave ports etc, where the DEPRECATED may be in the MASTER_PORT. Try this: #!/bin/sh # PO

Re: Re: saving a few ports from death

2011-04-27 Thread Chip Camden
Quoth Eitan Adler on Wednesday, 27 April 2011: > > What is not broken -- just old, like  databases/db2 or www/apache13*, for > > example -- should be left alone (until it becomes both broken and > > unmaintained). And even then, the removal should not be > > mass-scale/automatic... > > This recent

Re: saving a few ports from death

2011-04-27 Thread Doug Barton
On 04/27/2011 08:59, Mikhail T. wrote: What is not broken -- just old, like ... or www/apache13* apache13 is way past EOL, and the apache team is working hard to move the default to apache22, at which point I personally hope that apache13 dies a quick and painful death :) -- Nothin

Re: Re: saving a few ports from death

2011-04-27 Thread Eitan Adler
> What is not broken -- just old, like  databases/db2 or www/apache13*, for > example -- should be left alone (until it becomes both broken and > unmaintained). And even then, the removal should not be > mass-scale/automatic... This recent sweep was neither mass scale nor automatic. 536/22816 port

Re: Re: saving a few ports from death

2011-04-27 Thread Mikhail T.
On -10.01.-28163 14:59, Robert Huff wrote: It is also possible it is only important to a fairly small number ... but to those it is absolutely crucial. Or the port might become useful/essential/critical to somebody in the future... What is not broken -- just old, like databases/db2 or

Re: saving a few ports from death

2011-04-27 Thread Diane Bruce
On Wed, Apr 27, 2011 at 08:02:34AM -0700, Chip Camden wrote: > Quoth Eric on Wednesday, 27 April 2011: ... > > >> My search for "popularity" metrics is intended to point me, as a > > >> maintainer, to ports I might want to adopt now, rather than wait for > > >> someone to complain about them. Ever

Re: saving a few ports from death

2011-04-27 Thread Mehmet Erol Sanliturk
On Wed, Apr 27, 2011 at 1:00 AM, Mark Linimon wrote: > I need to migrate portsmon to another server so that we can start up > these periodic emails again. > > mcl > ___ > With the large number of ports to be maintained , tasks to be performed becomes

Re: saving a few ports from death

2011-04-27 Thread Chip Camden
Quoth Eric on Wednesday, 27 April 2011: > > From: Anton Shterenlikht > > Date: Wed, 27 Apr 2011 10:14:41 +0100 > > To: > > Subject: Re: saving a few ports from death > > > > On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: > >> > &

Re: saving a few ports from death

2011-04-27 Thread Eric
> From: Anton Shterenlikht > Date: Wed, 27 Apr 2011 10:14:41 +0100 > To: > Subject: Re: saving a few ports from death > > On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: >> >> My search for "popularity" metrics is intended to point me, a

Re: saving a few ports from death

2011-04-27 Thread Anton Shterenlikht
On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote: > > My search for "popularity" metrics is intended to point me, as a > maintainer, to ports I might want to adopt now, rather than wait for > someone to complain about them. Everything *I* use is already > maintained, so I've moved o

Re: saving a few ports from death

2011-04-27 Thread Baptiste Daroussin
> Where is the current list of deprecated ports? > You can find the deprecated ones here http://www.freshports.org/ports-deprecated.php and the one set to expire there : http://www.freshports.org/ports-expiration-date.php regards, Bapt ___ freebsd-port

Re: saving a few ports from death

2011-04-26 Thread Mark Linimon
I need to migrate portsmon to another server so that we can start up these periodic emails again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsub

Re: saving a few ports from death

2011-04-26 Thread Jason J. Hellenthal
Adam, On Tue, Apr 26, 2011 at 10:51:39PM -0500, Adam Vande More wrote: >On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > >> >> Garance A Drosehn writes: >> >> > Speaking of which, I haven't noticed the old lists of >> > "FreeBSD unmaintained ports which are currently marked broken"

Re: saving a few ports from death

2011-04-26 Thread Adam Vande More
On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > > Garance A Drosehn writes: > > > Speaking of which, I haven't noticed the old lists of > > "FreeBSD unmaintained ports which are currently marked broken" > > and > > "FreeBSD ports which are currently scheduled for deletion" > >

Re: saving a few ports from death

2011-04-26 Thread Robert Huff
Garance A Drosehn writes: > Speaking of which, I haven't noticed the old lists of > "FreeBSD unmaintained ports which are currently marked broken" > and > "FreeBSD ports which are currently scheduled for deletion" > > show up recently. I did have some mixup in my email account >

Re: saving a few ports from death

2011-04-26 Thread Garance A Drosehn
On 4/25/11 8:28 PM, martinko wrote: Ok, I skimmed through the list of deprecated ports Speaking of which, I haven't noticed the old lists of "FreeBSD unmaintained ports which are currently marked broken" and "FreeBSD ports which are currently scheduled for deletion" show up recently. I

Re: saving a few ports from death

2011-04-26 Thread Doug Barton
On 04/26/2011 15:09, Charlie Kester wrote: Now that I have my code proved out, I'm going to expand it to look at all unmaintained ports regardless of category. Any suggestions for where I should post the results? (That is, unless you think the bitbucket is the only suitable place for it.) As

Re: saving a few ports from death

2011-04-26 Thread Charlie Kester
On Tue 26 Apr 2011 at 15:15:54 PDT Jerry wrote: If no one steps up claiming to need the port, then good riddance. If on the other hand a user claims a valid use of the port, let them take responsibility for it or find someone who will. Leaving intact ports that either don't build, cannot be fetc

Re: saving a few ports from death

2011-04-26 Thread Jerry
On Tue, 26 Apr 2011 14:54:05 -0700 Doug Barton articulated: > On 04/26/2011 14:18, Robert Huff wrote: > > It is also possible it is only important to a fairly small > > number ... but to those it is absolutely crucial. > > Fair enough, then one of them needs to step forward to maintain the >

Re: saving a few ports from death

2011-04-26 Thread Charlie Kester
On Tue 26 Apr 2011 at 14:34:00 PDT Charlie Kester wrote: On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: FWIW, here are some popularity/vitality stats from freshmeat for unmaintained ports in the sysutils category. Drat, the mailinglist rejected the attachment. If anyone wants to see

Re: saving a few ports from death

2011-04-26 Thread Doug Barton
On 04/26/2011 14:18, Robert Huff wrote: It is also possible it is only important to a fairly small number ... but to those it is absolutely crucial. Fair enough, then one of them needs to step forward to maintain the port. :) FWIW, I think that the person who suggested deleting the por

Re: saving a few ports from death

2011-04-26 Thread Charlie Kester
On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of un

Re: saving a few ports from death

2011-04-26 Thread Charlie Kester
On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of unmaintained ports and manually check them against the popul

Re: saving a few ports from death

2011-04-26 Thread Robert Huff
Chip Camden writes: > > If you want to definitively ascertain the popularity of an application, > > just remove it from the ports structure and see how many users complain. > > There could be quite a delay in that reaction -- it might not hit > home until the port needs to be rebuilt.

Re: saving a few ports from death

2011-04-26 Thread Chip Camden
Quoth Jerry on Tuesday, 26 April 2011: > On Tue, 26 Apr 2011 09:34:24 -0700 > Charlie Kester articulated: > > > It's a bit of a leap to assume that a program that's popular on Linux > > will be as popular on BSD, but it's the best data we have for the time > > being. > > If you want to definitiv

Re: saving a few ports from death

2011-04-26 Thread Jerry
On Tue, 26 Apr 2011 09:34:24 -0700 Charlie Kester articulated: > It's a bit of a leap to assume that a program that's popular on Linux > will be as popular on BSD, but it's the best data we have for the time > being. If you want to definitively ascertain the popularity of an application, just re

Re: saving a few ports from death

2011-04-26 Thread Charlie Kester
On Mon 25 Apr 2011 at 22:55:10 PDT Ade Lovett wrote: On Apr 25, 2011, at 21:41 , Charlie Kester wrote: Maybe freshports could implement a voting system like the one at osx.iusethis.com? "Voting" implies some kind of democracy. I just thought it might be useful to get some actual data to sup

Re: saving a few ports from death

2011-04-25 Thread Ade Lovett
On Apr 25, 2011, at 21:41 , Charlie Kester wrote: > Maybe freshports could implement a voting system like the one at > osx.iusethis.com? "Voting" implies some kind of democracy. This may come as a shock to folks, but FreeBSD in general is in fact not democratic. It's based around the concept o

Re: saving a few ports from death

2011-04-25 Thread Ruslan Mahmatkhanov
26.04.2011 04:28, martinko пишет: Ok, I skimmed through the list of deprecated ports and I identifed the following that I may be using or at least used in past and I could take over their maintenance to save them from death: graphics/gimp-greycstoration Use graphics/gimp-gmic-plugin instead. Pl

Re: saving a few ports from death

2011-04-25 Thread Charlie Kester
On Mon 25 Apr 2011 at 17:48:31 PDT Doug Barton wrote: What we're trying to do here is to eliminate ports that are no longer useful. If we had some popularity stats, it would be interesting to see where the unmaintained ports fall on the list. Unfortunately, bsdstats doesn't include this anymor

Re: saving a few ports from death

2011-04-25 Thread Jeremy Messenger
On Mon, Apr 25, 2011 at 7:48 PM, Doug Barton wrote: > On 04/25/2011 17:28, martinko wrote: >> >> Ok, >> I skimmed through the list of deprecated ports and I identifed the >> following that I may be using or at least used in past and I could take >> over their maintenance to save them from death: >

Re: saving a few ports from death

2011-04-25 Thread Doug Barton
On 04/25/2011 17:28, martinko wrote: Ok, I skimmed through the list of deprecated ports and I identifed the following that I may be using or at least used in past and I could take over their maintenance to save them from death: Generally by the time that a port has deteriorated to the point whe