Hi,
Reference:
> From: Doug Barton
> Date: Sat, 10 Sep 2011 01:40:27 -0700
> Message-id: <4e6b227b.5050...@freebsd.org>
Doug Barton wrote:
> The way that the FreeBSD project handles deleted ports is to leave them
> in the CVS repository, where they are easily available to eve
On Sat, 10 Sep 2011 14:30:16 +0100
Chris Rees wrote:
> On 10 September 2011 10:46, Alberto Villa wrote:
> > On Saturday 10 September 2011 10:53:54 Chris Rees wrote:
> >> I also don't think this is a terrible idea, but perhaps we could
> >> just put a little section about Resurrecting dead ports
On 2011-09-12 01:22, Doug Barton wrote:
> On 09/11/2011 13:35, Warren Block wrote:
>> Let me suggest a reasonable[1] plan:
>
> No. :) No more talking is necessary. Doing is necessary (or not,
> doesn't really matter to me at this point).
>
> I think Chris is right, a reasonable first step is a H
On Sun, 11 Sep 2011 14:35:47 -0600 (MDT)
Warren Block wrote:
> If archival of old historical distfiles is needed, that's not really
> a FreeBSD problem. Start a new project with its own website. Quick,
> somebody register deadports.org![4]
LOL. Love the name! Wonder if it's already taken.
On 09/11/2011 13:35, Warren Block wrote:
> Let me suggest a reasonable[1] plan:
No. :) No more talking is necessary. Doing is necessary (or not,
doesn't really matter to me at this point).
I think Chris is right, a reasonable first step is a Handbook section on
"How to recover a port from the CV
On Sun, 11 Sep 2011, Chris Rees wrote:
On 11 September 2011 15:35, Warren Block wrote:
On Sun, 11 Sep 2011, Greg Byshenk wrote:
On Sat, Sep 10, 2011 at 01:05:49PM -0600, Chad Perrin wrote:
Why?
Because, in the cases here under discussion, there is somethin "wrong"
(for some value of 'wro
Just a case study. I was updating today,
turns out print/mgv was deleted, so I switched
to print/gv. The end.
The current port deletion policy needs no change.
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 3
On 11 September 2011 15:35, Warren Block wrote:
> On Sun, 11 Sep 2011, Greg Byshenk wrote:
>>
>> On Sat, Sep 10, 2011 at 01:05:49PM -0600, Chad Perrin wrote:
>>>
>>> Why?
>>
>> Because, in the cases here under discussion, there is somethin "wrong"
>> (for some value of 'wrong') with the software i
On Sun, 11 Sep 2011, Greg Byshenk wrote:
On Sat, Sep 10, 2011 at 01:05:49PM -0600, Chad Perrin wrote:
Why?
Because, in the cases here under discussion, there is somethin "wrong"
(for some value of 'wrong') with the software in question. I can't
speak for Matthias or Chris, but I think the po
On Sat, Sep 10, 2011 at 01:05:49PM -0600, Chad Perrin wrote:
> On Sat, Sep 10, 2011 at 06:48:30PM +0100, Chris Rees wrote:
> > On 10 September 2011 18:15, Chad Perrin wrote:
> > > On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
> > >>
> > >> I want to make installing dead ports ha
On 11 Sep 2011 00:14, wrote:
>
> Chris Rees wrote:
>
> > cvsweb can also be used to find the day the port was deleted.
>
> Shouldn't that date be available in the MOVED entry?
>
Hm, indeed, and creative use of read and expr could automate that.
Chris
Chris Rees wrote:
> cvsweb can also be used to find the day the port was deleted.
Shouldn't that date be available in the MOVED entry?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, se
On Sat, Sep 10, 2011 at 06:48:30PM +0100, Chris Rees wrote:
> On 10 September 2011 18:15, Chad Perrin wrote:
> > On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
> >>
> >> I want to make installing dead ports harder for users.
> >
> > Why?
>
> Someone who wants to install a port t
I was thinking of this problem, and i believe compressed file is not the
solution, since the ports tree infrastructure changes, and that removed
ports should be changed also. The second problem is where to store
distfiles? Because the majority (nb: not all of them) of removed ports
it's a dis
On 10 September 2011 19:39, Warren Block wrote:
> On Sat, 10 Sep 2011, Chris Rees wrote:
>
>> On 10 September 2011 18:15, Chad Perrin wrote:
>>>
>>> On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
I want to make installing dead ports harder for users.
>>>
>>> Why?
>>>
>
On Sat, 10 Sep 2011, Chris Rees wrote:
On 10 September 2011 18:15, Chad Perrin wrote:
On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
I want to make installing dead ports harder for users.
Why?
Someone who wants to install a port that has been deprecated and
removed sho
On 10 September 2011 18:15, Chad Perrin wrote:
> On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
>>
>> I want to make installing dead ports harder for users.
>
> Why?
>
Someone who wants to install a port that has been deprecated and
removed should really have enough skills to ch
On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
>
> I want to make installing dead ports harder for users.
Why?
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
pgpVidnJd8Edb.pgp
Description: PGP signature
Am 10.09.2011 10:40, schrieb Doug Barton:
> The way that the FreeBSD project handles deleted ports is to leave them
> in the CVS repository, where they are easily available to everyone who
> would like to access them.
>
> However I think that your idea is interesting, and I'd love to see the
> peo
On 10 September 2011 10:46, Alberto Villa wrote:
> On Saturday 10 September 2011 10:53:54 Chris Rees wrote:
>> I also don't think this is a terrible idea, but perhaps we could just
>> put a little section about Resurrecting dead ports with a quick cvs
>> tutorial into the Porter's Handbook?
>
> wh
On Saturday 10 September 2011 10:53:54 Chris Rees wrote:
> I also don't think this is a terrible idea, but perhaps we could just
> put a little section about Resurrecting dead ports with a quick cvs
> tutorial into the Porter's Handbook?
why not writing a make target in bsd.port.mk to do it? cvs i
On 10 September 2011 09:40, Doug Barton wrote:
> The way that the FreeBSD project handles deleted ports is to leave them
> in the CVS repository, where they are easily available to everyone who
> would like to access them.
>
> However I think that your idea is interesting, and I'd love to see the
The way that the FreeBSD project handles deleted ports is to leave them
in the CVS repository, where they are easily available to everyone who
would like to access them.
However I think that your idea is interesting, and I'd love to see the
people who are deeply concerned about deleted ports pursu
I've seen many requests of late, for ports that are no longer in active
development, abandoned etc
but still working, but they've been removed from ports.
here's an idea, I don't know if this has been discussed before.
It requires work of course. But doesn't require a person to know how to
develop
24 matches
Mail list logo