>> One thing we could do would be to implement extensions to >> the Dependencies format _first_ and worry about use-flags later. >> >> How about something adding a bracketed list of tags, like: >> >> Foo >= 1.0, < 2.0 [build-only, optional, i686] >> Bar >= 0.3.5 [runtime-only, !ppc]
okay, then is this interpretation okay? [i686, x86_64] means it applies in either case [!i686, !x86_64] means the arch can't be either [!i686, x86_64] is meaningless --> if your arch is mentioned positively, pass --> if your arch is mentioned negatively, fail otherwise, --> if another arch is mentioned positively, fail --> if another arch is mentioned negatively, pass otherwise, pass and there would be a well-known list of what the architectures are. (multiple arches in one line could be forbidden, at the price of requiring more dependency-line duplication if we end up supporting a lot of arches - more than two or three - in our recipe store) Isaac _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
