[IDEA] How to represent package version dependencies?
Andreas Kohn
andreas.kohn at gmx.net
Sat Feb 26 18:28:18 GMT 2005
On Sat, 2005-02-26 at 23:39 +0800, Xin LI wrote:
> Ah... I just know that from the porters' handbook and bsd.port.mk :-)
> I'd personally prefer file:package[< | = | > )version][:target] scheme,
> since it looks more straightforward.
I also like this scheme better.
Actually, I was thinking about something similar:
I wanted to create some shell script which runs over the ports tree,
figures out the current version of a port, and creates a second ports
hierarchy from it:
/usr/vports/<cat>/<port>/<port-name+version>
A Makefile in /usr/vports/<cat>/<port> would build the latest version,
but every versioned port would know against which other port versions it
depended, and would use these versions.
Some changes to bsd.port.mk (i.e. /usr/ports/Mk/*.mk + patches
-> /usr/vports/Mk/*.mk) would have to handle parts of the versioning.
Unfortunately, there were many problems that surfaced when thinking
about this a little bit more, most of them related to optional
dependencies, and management problems, so I did not start actually
trying to build this.
But at least requiring a certain minimum version would certainly be
nice!
Regards,
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050226/fb842e25/attachment.bin
More information about the freebsd-ports
mailing list