-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michèle Garoche wrote:
| | Le 18 juin 2004, à 15:48, Benjamin Reed a écrit : | |> I agree that anything that's got headers for development in it should be |> BuildDependsOnly. As I understand it, there are some packages that use |> headers at runtime, but, IMHO, the headers should be duplicated in |> /sw/share as data in that particular case. | | Does it apply in the case of cssed? I mean do you consider the fact that | there are headers in /sw/include implies obligatorily that the headers | are meant for development. (Actually they are meant for development but | just for cssed development, not for any other package).
Well, it implies that they're reachable by other packages trying to build things from source; I would say that as long as they're in a "public" place that other packages can end up linking against, they should be BuildDependsOnly. If you *also* need them as some kind of runtime reference, then make a copy to treat as data files, that can be supplied with the runtime portion of the package.
- -- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA0vodUu+jZtP2Zf4RAviCAJ4kEOQlEEMcuI94iezge5zzFmGxPACdFqxD 6eTf7Io2/B39ZF9DwQVg5XY= =bTLq -----END PGP SIGNATURE-----
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
