Uhm, it seems I made myself not at all clear, almost all of the replies I have read so far have at least in one point not understood what I meant, so I assume it was my fault :) Let me reply to all in this single mail:
At 8:37 Uhr -0500 08.02.2002, David R. Morrison wrote: >How about if the package installs a shell script in %i/bin which detects >the version number, and then this shell script is called in post-install? ThIn other words, you suggests creating an actual package. But the point always was that these packages would allow us to do a "Depends: Darwin (>=1.4)" which would not be possible this way (a post-install script can't change the package version) At 23:01 Uhr +0900 08.02.2002, Peter O'Gorman wrote: >I personally think that this package should provide libSystem, >Carbon, Cocoa and so on, each with the installed version. Packages >should then depend on the OS features that they need, rather than >the operating system version. I don't see any justification for this. First off, the darwin and macosx package are not really meant to detect the presence/absence of stuff like Carbon etc., but rather, they are meant to allow packages that require a certain kernel version (e.g. gnupg for /dev/random) to gurantee they won't be installed on older systems. Discussing the possible need for a way to allow packages to specify they require Carbon/Cocoa is certainly interesting, but not exactly what these pseudo packages are meant for. >Fink builds a package for itself using the injext.pl script. A dpkg >package for whatever is on the users system could be built by fink >when it is updated/installed. A systemupdate script could be >supplied to rebuild this package when the user updates her OS. That won't work with a shared fink folder. I pointed that out in my original mail I believe :) >There is another problem: >Some packages must change stuff outside of /sw, postfix being one >example. These packages could have a systemupdate script that gets >called whenever the user uses the systemupdate command...?? You should start a seperate thread on this, it is not directly related to the discussion at hand. At 9:07 Uhr -0700 08.02.2002, Justin Hallett wrote: >well debian has pseudo packages as you call them, they are -task packages, >maybe we should see how they are made?? > -task packages correspond to our virtual packages. We already have that for a long time. The issue here is different, because the version of the darwin/macosx packages are to be determined on the fly. The versions of "normal" virtual packages are static, though. So, to sum it up: these two packages need a dynamic version. The more I think about it, the more it seems the only way to achieve it is a change to dpkg. 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
