From owner-freebsd-ports Sun Oct 21 6:21:52 2001 Delivered-To: freebsd-ports@freebsd.org Received: from smtp6.port.ru (mx6.port.ru [194.67.57.16]) by hub.freebsd.org (Postfix) with ESMTP id 9F13237B409 for ; Sun, 21 Oct 2001 06:21:48 -0700 (PDT) Received: from [213.133.160.239] (helo=notebook.vega.com) by smtp6.port.ru with esmtp (Exim 3.14 #1) id 15vIXt-000Kjp-00; Sun, 21 Oct 2001 17:21:45 +0400 To: rendhalver@users.sourceforge.net, ports@FreeBSD.ORG From: Maxim Sobolev Reply-To: sobomax@FreeBSD.org Subject: Re: new cvs based port idea X-Mailer: Pygmy (v0.5.13) Date: Sun, 21 Oct 2001 16:21:31 EEST In-Reply-To: <15314.31549.46794.529610@ulthwe.dyndns.org> Message-Id: Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 21 Oct 2001 17:37:33 +1000, Peter Brown wrote: > hi all > > i have been toying with the idea of writing a port for mozilla using > cvs to get the source instead od having to download the 25+ meg bzip > on each upgrade. > > having to download a 25+ meg file for mozilla each time is begining to > annoy me, especially when a cvs version would make it quicker. > > the idea i had is as follows > > rewrite the port so that it does a cvs -z3 update -r "RELEASE_TAG" > when the version changes. > > i also thought of submitting the patches to the mozilla developers > that would make updating the port a simple matter of updating the > PORTVERSION as the CVS tag will be based on that. While it may sound like a brilliant idea, in fact it creates more problems than solves. Following are the most obvious of those problems: - often Mozilla developers are reapplying the same tag after a several days from the initial release, which we now could detect by the checksum mismatch, but would have no way to notice in the distfile is replaced with the cvs; - this will mean that the user will need to permanently keep Mozilla cvs tree (some 200MB) around, which is not what many users want to do; - what will happen is the Mozilla cvs server goes off-line for some reason? Now we have several mirrors that could be used instead, which is much harder to implement in the cvs case. All this would lead to a decresed port's reliability and as a result increased load on the Mozilla FreeBSD maintainers, thus it is likely that we will have to reject your changes. I'm really sorry, but it's true. If you really have a bad bandwith you can unpack tarball from the previous version, do `cvs update', reroll the tarfile, adjust Mozilla's distinfo accordingly and build the port. > i also with to put switches in to disable the mail/news portions of > mozilla or having it not build them by default to make the port > smaller and quicker than the 5-6 hours it currently takes to build on > my machine. i realise this will change the pkg-plist file, i will > workout how that can be split into sections. > > i have not completed my port yet but i will submit it when i believe > it is ready, whick should be soon (2 weeks maximum). This is a better idea, I will take a look at the patches when they arrive. Thanks! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message