At 15:06 Uhr -0500 18.01.2002, David R. Morrison wrote: >On the question of variants, there is one thing that is very important >to keep in mind: fink is a front-end to dpkg. > >This means that whatever scheme we adopt, there will need to be a translation >to dpkg names. > >If we are feeding dependency information to dpkg, for example, all of >that information will need to be translated to dpkg names.
Did you fully read my email? I actually talked about this in it :) > > >A simple scheme of variants for a single fink package foo, could have >variants A, B, C leading to dpkg packages foo-A, foo-B, foo-C, for >example. dpkg would be told that all of these "Provide: foo." Yes. >I start to get nervous about inheritance, though, under these circumstances. >It could lead to some very complicated situations. "Inheritance" as I suggested it is completly transparent to dpkg, it doesn't have to know anything about it. The inheritance thingy is just a way to prevent the need to specify options multiple times. This eases package creations, prevents one from forgetting to duplicate stuff, and also lowers the information redundancy. Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
