Date: Fri, 11 Jun 2010 17:41:45 +0300 From: Peter Pentchev <roam@ringlet.net> To: Greg Larkin <glarkin@FreeBSD.org> Cc: freebsd-ports <freebsd-ports@FreeBSD.org>, Jesse Smith <jessefrgsmith@yahoo.ca> Subject: Re: Data files and ports Message-ID: <20100611144144.GA4167@waylight.m.ringlet.net> In-Reply-To: <4C12458A.10109@FreeBSD.org> References: <1276264730.2503.20.camel@hp-laptop> <4C12458A.10109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 11, 2010 at 10:17:46AM -0400, Greg Larkin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Jesse Smith wrote: > > I'm trying to teach myself how to build a FreeBSD port and, with a lot > > of help from the manual, it's going well. I have a question though > > concerning policy/style. > >=20 > > I'm trying to port a program which is distributed in two separate > > packages from the upstream project. One package contains the executable > > program and the other contains data files. The Data package rarely > > changes. The idea being packaging them together would use up a lot of > > extra bandwidth. > >=20 > > Which brings me to the question: Since the executable relies on the data > > files being in place before it's run, how should I handle that in the > > port? Should I just get the executable to install and let the user > > manually get the data files? Should I create a second port for the data > > package? Or should I find some way of making the executable's makefile > > download and unpack the data package? > >=20 > > My instinct is to create a separate port for the Data package and list > > it as a dependency for the Executable port. I'd appreciate some > > guidance. > >=20 > > Thanks. >=20 > Hi Jesse, >=20 > Welcome to the fray, and I'm glad to hear that you're learning how to > develop FreeBSD ports! >=20 > To answer your question - your port Makefile can download multiple > distribution files from the upstream download site. For a couple of > examples, see these Makefiles: [snip] All good points, and good examples. However... :) Well, I do believe that if "the Data package rarely changes", then it would be unnecessary not only to distribute it each time as a port's source distfile, but also to include it (unchanged) in different releases of the *packages* that the port builds. Thus, IMHO it would be best to make a separate port for the data file and have the main program (port) depend on it. This would make sure that not only people who build the port "by hand" do not download the data file more often than necessary, but also the people who use packages do not download needlessly big packages for each program update with no data change. Hope that came out clear enough; I know I'm not thinking straight today. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@space.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJMEksjAAoJEGUe77AlJ98T62kQAL2Nxd9hSJPG7I5iixWgVYzX MEtnkMQhwEOfPi7MckCUiENLQ5hpJhzTWgiLG3/xuhzDnwQZtwxlr3shQuE2eQqN 3bghdjTUr6AupOq3knLcY0/lTSp+OzzAGvP+Hidcfj70sweHqu9yCPmn+NSCaCFY DuIC2r4kArAplyKZykYJw99TxRBj1XofOGQDOCyIuMUv/oE8Dmjk73GBPTFAcIve 7xr6KPehhAphlmq8UuEZt6Z0Uv2X6sXn3zYRJAS0qPeaDuvMBLP0A7foeLO4GSal 0L5oVxBpU+B9E0EovnBIZWzGCYqCSvKCE72w+2xgZnJuT3Q4zNfLj1z6vTXh/5vc w0XMpoNfROZp3mO8xR12d7PEaYujNcAFRSac4uidSgzBOycw1YQJDDkFkMB2zf1I AhOEN67yUr5ty2wUC3kwnNY2/G1wR47zMRjkkXdO+rm+WoMg8cZVN0DA12WQcv82 //OvNqbz4pZPiQdCOciXU/DcvAxwMpvS0msTMbIKKc2v7sBj65nfnrkYZhXUg1ru YGKr6+mBuPRskkVayFII+E0q+wPFlpsuSuilRh5k3UnzmOdE99bZnnU6GLDXXw11 QDLSkdgpCYIl8fshkT330z1y5kOtHBFFpfJGsB7QmTCLc8y/siW+mIJgSyQFB3RV M/NofDPg/i55Y4ugtne1 =Y1FY -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100611144144.GA4167>