I've modified the proposed policy in response to today's feedback (and 
after a bit of coding for the forthcoming fink 0.20.5).  Further discussion
and feedback are most welcome.

  -- Dave


Second draft:
The BuildDependsOnly field

When libraries are being upgraded over time, it is often necessary to have
two versions of the header files available during a transition period,
with one version used for compiling some things and the other version
used for compiling others.  For this reason, the packages containing
header files must be constructed with some care.  If both foo-dev and
bar-dev contain overlapping headers, then foo-dev should declare
  Conflicts: bar-dev
  Replaces: bar-dev
and similarly bar-dev declares Conflicts/Replaces on foo-dev.

In addition, both packages should declare
  BuildDependsOnly: true
This inhibits others from writing packages which depend on foo-dev or
bar-dev, since any such dependency will prevent the smooth operation of the
Conflicts/Replaces method.

There are some packages containing header files for which it's not
appropriate to declare BuildDependsOnly to be true.  In that case,
the package should declare
  BuildDependsOnly: false
and the reason must be given in the DescPackaging field.

The BuildDependsOnly field should only be set if the package contains
header files, installed into /sw/include.

As of fink 0.20.5, "fink validate" will issue a warning for any .deb
which contains header files and at least one dylib, and does not declare
BuildDependsOnly to be either true or false.  (It is possible that in
future versions of fink, this warning will be expanded to cover the case of
a .deb with header files and a static library as well.)



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to