Actually the mozilla products fetches are done via ftp. The right way to do it is via http, because sometimes some people can be in a place where they can't use the port 21.
IMHO we should provide both protocols. Right now we have MOZ_FTP_URI which is used in mozlinguas.eclass. How about adding a MOZ_HTTP_URI variable and add both URIs to SRC_URI variable?
(In reply to comment #1) > IMHO we should provide both protocols. > > Right now we have MOZ_FTP_URI which is used in mozlinguas.eclass. > > How about adding a MOZ_HTTP_URI variable and add both URIs to SRC_URI > variable? Is rather useless, http does not allow us to control the package, packages are always avaliable via ftp they are removed from http side when upstream is done and makes next release.
(In reply to comment #2) > (In reply to comment #1) > > IMHO we should provide both protocols. > > > > Right now we have MOZ_FTP_URI which is used in mozlinguas.eclass. > > > > How about adding a MOZ_HTTP_URI variable and add both URIs to SRC_URI > > variable? > > Is rather useless, http does not allow us to control the package, packages > are always avaliable via ftp they are removed from http side when upstream > is done and makes next release. Is this true for the http://ftp.mozilla.org/pub/mozilla.org/ site?
my bad, there is nothing to do with the eclass. We have the ftp:// directly in the ebuilds.
How about we add both, ftp _and_ http download URLs to the ebuilds/eclasses? As long as we use "http://ftp.mozilla.org/..." older releases should still be fetchable.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
