Migration to new SourceForge url scheme now inevitable, solution

[Ion-Mihai Tetcu]

On Fri, 21 Aug 2009 09:06:18 +0200
Pav Lucistnik <pav at FreeBSD.org> wrote:

> Dmitry Marakasov píše v pá 21. 08. 2009 v 07:50 +0400:
> 
> > [1] http://people.freebsd.org/~amdmi3/sfp.patch
> > [2] http://people.freebsd.org/~amdmi3/sfp.log
> 
> This looks good so far.
> 
> > PS. Btw, SOURCEFORGE_EXTENDED and SOURCEFORGE_JP still use an old
> > scheme. Because of that SFE can no longer include SF, and honestly,
> > I
> 
> JP is completely separate thing, so I'd leave it alone for now.
> SF_E can be axed if all the files fetch from regular SF. IIRC there
> were some projects in the past that were only distributed on SF_E
> sites, not on SF sites?

From what I remember SF_E were carrying only part of the things
available on SF. 


-- 
    (__)      IOnut       (__)
    (.''///            \\\'',)
  ^ /  \/                \/  \ ^
  (_\. /.                .\. /_)
  ==============================
BOFH excuse #400:

We are Microsoft.  What you are experiencing is not a problem; it
is an undocumented feature.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20090821/8308cc18/signature.pgp