Mail Archives: djgpp-workers/2001/12/26/06:14:29
Hello.
Eli Zaretskii wrote:
> Sorry, you lost me: how does /dev/env/MY_VAR relates to what you put
> in "provides:" in a DSM?
>
> I thought "provides:" is a sibling to "requires:". That is, when
> zippo has to satisfy the set of "requires:" directives, it looks for
> packages which "provide" the required features. Did I miss something?
You are exactly right about "provides" being used to say what features a
package has. So for CWSDPMI we have "provides: DPMI" in CWSDPMI's DSM [in
zippo CVS]. Then packages have "requires: DPMI". This is so packages can
have "requires: DPMI" rather than "requires: cwsdpmi", which would prevent
people using any DPMI provider.
/dev/env/MY_VAR is a feature provided by djdev 2.03, but not earlier
versions. It's one of the standard provisions listed in the DSM
specification: "djgpp-dev-env". djdev 2.03 provides the /dev/env/MY_VAR
feature, so we put a "provides: djgpp-dev-env" line in the djdev 2.03 DSM.
If you're building something that requires this feature to be present in
libc, e.g., Perl 5.6, then you'll want "requires: djgpp-dev-env" in that
package's source distribution.
Actually, now I think about it, I don't understand why the Perl 5.6
binaries package has "requires: djgpp-dev-env" in its DSM. Since it must
have been built with DJGPP 2.03, the binaries will support djgpp-dev-env.
But the sources package has "requires: djgpp-dev-env", which is OK.
I hope that makes things clearer.
Bye, Rich =]
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -