From owner-freebsd-questions@FreeBSD.ORG Mon Jan 2 22:26:37 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B13D16A41F for ; Mon, 2 Jan 2006 22:26:37 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.187.76.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B29E43D49 for ; Mon, 2 Jan 2006 22:26:35 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from [IPv6:::1] (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.13.4/8.13.4) with ESMTP id k02MQO95064511; Mon, 2 Jan 2006 22:26:25 GMT (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <43B9A88A.8010401@infracaninophile.co.uk> Date: Mon, 02 Jan 2006 22:26:18 +0000 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051221) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam Nealis References: <20060102154757.68716.qmail@web86906.mail.ukl.yahoo.com> In-Reply-To: <20060102154757.68716.qmail@web86906.mail.ukl.yahoo.com> X-Enigmail-Version: 0.93.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig35CA3B58B1961704ED22B370" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.infracaninophile.co.uk [IPv6:::1]); Mon, 02 Jan 2006 22:26:25 +0000 (GMT) X-Virus-Scanned: ClamAV 0.87.1/1225/Mon Jan 2 17:54:07 2006 on happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on happy-idiot-talk.infracaninophile.co.uk Cc: freebsd-questions@freebsd.org Subject: Re: How should a non-port maintainer submit a binary package for a port? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:26:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig35CA3B58B1961704ED22B370 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Adam Nealis wrote: > Having just taken the plunge and updated my world to 6.0-STABLE on one of > my boxen, I'm going through the process of installing gnome2 et al. I've > used > > portinstall -Pp > > so as to end up with packages for everything I install so that I can more > quickly update my other box from 5.4-RELEASE to 6.0-STABLE + packages. > > Since I'll soon have used up a lot of time building binary packages, it > occurred to me that it might be useful to submit these packages to the > official repositories. > > But the question is "How?". > > Do I have to contact the port maintainer? > > Would the maintainer trust me? Thank you for the offer, but I'm afraid you're on a hiding to nothing here. Individual port maintainers have almost no control over whether and when binary packages are created from the ports they maintain -- other than the basic "License Terms forbid redistribution in Binary Form" sort of thing. Control of what does go onto the FreeBSD FTP servers rests with the 'portmgr' team: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-listing.html But don't try e-mailing them directly as they are incredibly busy people: use the freebsd-ports@freebsd.org mailing list instead for ports related discussions. The FreeBSD project has quite a number of package building machines spread around the world. Those are the only machines trusted to generate the packages available on the FreeBSD web/FTP servers. Permitting just anybody to submit precompiled packages would be a security nightmare: how would you ensure that the compiled code hadn't been built from trojanned sources? As complete a set of packages as possible is built just prior to each release. Packages are also built regularly for the main development branches. Updated packages are built where ports get updated between the main package building runs although the time lag on that can be several weeks. Packages are built for all tier-1 architectures and for the latest releases from supported branches (currently 5.4 & 6.0) as well as the active development branches (4-STABLE, 5-STABLE, 6-STABLE and HEAD (a.k.a 7-CURRENT)) -- the FTP servers currently say this: 250-These are packages for the i386 architecture. Here are brief 250-descriptions of each subdirectory. 250- 250- packages-4-stable: Packages for FreeBSD-4-stable. 250- packages-4.11-release: Packages for FreeBSD 4.11-release. 250- packages-5-stable: Packages for FreeBSD-5-stable. 250- packages-5.4-release: Packages for FreeBSD 5.4-release. 250- packages-6-current: Packages for FreeBSD-6-current. 250- packages-7-current: Packages for FreeBSD-7-current. 250- 250-packages-*-release directories are built from the ports collection 250-shipped with the release, and are not updated thereafter. but that's a little out of date as it's packages-6.0-release and packages-6-stable nowadays and there isn't a packages-4.11-release directory any more. There's a detailed description of the build procedures here: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/portbuild/index.html and a big database of results of running all those builds here: http://pointyhat.freebsd.org/errorlogs/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig35CA3B58B1961704ED22B370 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDuaiQ8Mjk52CukIwRA49xAJ0V1tEL4D6BRXwPZ7dpWrq3/4gfgQCfQsBN 52Plgm2yvANPJqXpIgtlp2A= =77MN -----END PGP SIGNATURE----- --------------enig35CA3B58B1961704ED22B370--