At 20:30 Uhr -0500 08.02.2002, Alexander Strange wrote:
>*looks ashamed*
>Err, I do that. But only because there isn't any room left on my
>internal disk.
That is perfectly OK IMHO, and it worked well for me in the past, too.
Max
--
---
Max Horn
Sof
*looks ashamed*
Err, I do that. But only because there isn't any room left on my
internal disk.
On Friday, February 8, 2002, at 06:48 PM, Justin Hallett wrote:
> I don't understand this shared install thing?? one HD multisystems.
> This
> should never be in finks intressed anyhow, debian coul
At 11:24 Uhr +1100 09.02.2002, [EMAIL PROTECTED] wrote:
>On Saturday, February 9, 2002, at 10:45 AM, Peter O'Gorman wrote:
>
>>>
>>>That won't work with a shared fink folder. I pointed that out in
>>>my original mail I believe :)
>>Yes, I really ought to learn to read...
>>
>>Fink could write to
On Saturday, February 9, 2002, at 10:45 AM, Peter O'Gorman wrote:
>>
>> That won't work with a shared fink folder. I pointed that out in my
>> original mail I believe :)
> Yes, I really ought to learn to read...
>
> Fink could write to /sw/var/lib/dpkg/available directly (this isn't
> going t
At 8:45 Uhr +0900 09.02.2002, Peter O'Gorman wrote:
>>That won't work with a shared fink folder. I pointed that out in my
>>original mail I believe :)
>Yes, I really ought to learn to read...
>
>Fink could write to /sw/var/lib/dpkg/available directly (this isn't
>going to be shared).
>Changing d
If some package which the user wants depends on (darwin51 | darwin52),
the user will be forced to install one or the other.
-- Dave
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
but this is assuming that the user knows to install darwin52
[EMAIL PROTECTED] writes:
>Actually, Justin, it is just fine for the binary distribution. The script
>in question will get installed by a package like darwin52 I mentioned
>before; other things can depend on it; so even users using apt
Actually, Justin, it is just fine for the binary distribution. The script
in question will get installed by a package like darwin52 I mentioned
before; other things can depend on it; so even users using apt-get will
have this package. They are *all* instructed to put "source /sw/bin/init.csh"
in
one again no good for bind dist.
[EMAIL PROTECTED] writes:
>OK, how about if the script runs when the user sources /sw/bin/init.csh .
>It is silent if the test passes, otherwise it warns you that the system
>has changed and things should be upgraded.
¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·.,
I don't understand this shared install thing?? one HD multisystems. This
should never be in finks intressed anyhow, debian couldn't even do that.
[EMAIL PROTECTED] writes:
>That still doesn't work in an install that is shared between multiple
>systems. Plus it requires the user to do a change
OK, how about if the script runs when the user sources /sw/bin/init.csh .
It is silent if the test passes, otherwise it warns you that the system
has changed and things should be upgraded.
-- Dave
___
Fink-devel mailing list
[EMAIL PROTECTED]
https:/
At 18:34 Uhr -0500 08.02.2002, David R. Morrison wrote:
>package darwin52 checks in post-install (by running script) if it is
>darwin 5.2 which is on the system. If not, it gives an error and
>the package doesn't install.
>
>(with an informative message suggesting to install darwin51 or whatever)
>
> That won't work with a shared fink folder. I pointed that out
> in my original mail I believe :)
Yes, I really ought to learn to read...
Fink could write to /sw/var/lib/dpkg/available directly (this
isn't going to be shared).
Changing dpkg doesn't seem like the "right thing".
Peter
unless we add this in fink it's self with a fink base-upgrade which will
run the checks and find the closest pkgs. That could be done, but then we
have the dpkg problem.
[EMAIL PROTECTED] writes:
>package darwin52 checks in post-install (by running script) if it is
>darwin 5.2 which is on the sy
okay so we need to determ the system versions, so make a configure file
that will fail if no >= a certain version
then of course the sucky part we need a Darwin1.3, 1.4 and 5.2 etc etc and
the user has to install the pkg...that is off the top of my head i know
sucks but it's a starting point so t
package darwin52 checks in post-install (by running script) if it is
darwin 5.2 which is on the system. If not, it gives an error and
the package doesn't install.
(with an informative message suggesting to install darwin51 or whatever)
we would need to give users advice, separately, that whenev
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 p
this is an idea with merit, what do you think the script should look like
or return as a value?
[EMAIL PROTECTED] writes:
>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?
¸.·´^`·.,][JFH][`·.,¸¸.·´
well debian has pseudo packages as you call them, they are -task packages,
maybe we should see how they are made??
[EMAIL PROTECTED] writes:
>There is a problem with the two pseudo packages darwin and macosx -
>they don't work for the binary distro.
>
>Reason: these pseudo packages are only visi
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.
Fink builds a package for itself using the injext.pl script. A
dpkg
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?
-- Dave
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink
There is a problem with the two pseudo packages darwin and macosx -
they don't work for the binary distro.
Reason: these pseudo packages are only visible to Fink, not to dpkg.
The first simple solution would be to make them visible by inserting
fake descriptions into dpkg's database, but that
22 matches
Mail list logo
