One correction to the earlier proposal. In the section on upgrading, I
should have said:
If shared libraries (or any other files now present
in foo-shlibs) were installed previously, then these new packages should
say
Replaces: foo (<< earliest. compliant.version)
so that upgra
Hi Dave,
Could you include an actual example (e.g. libpng) in this
policy. It would make it easier to follow.
It might just be me on a Monday morning, not thinking straight though :)
I think it is good that shared libs are getting sorted out.
Peter
On Monday, February 4, 2002, at 05:25 AM,
> What about the case where it is the binaries in the package that are
> depended upon?
>
> EG: Some new package might consist of a number of python scripts, thus
> pythonN would be be required.
This part of the policy only applies to packages supplying shared libraries.
As it says a bit furthe
On Monday, February 4, 2002, at 07:25 AM, David R. Morrison wrote:
> Depends: barN-shlibs
> BuildDepends: barN
> It will not be permitted for another package to depend on barN itself.
What about the case where it is the binaries in the package that are
depended upon?
EG: Some new package
At 15:25 Uhr -0500 03.02.2002, David R. Morrison wrote:
>Based on the discussion which Max and I had on this list yesterday, I have
>drawn up a proposed new policy document for shared libraries in fink.
>If we all agree on this, I would propose to add it to the packaging manual
>as a new subsectio
