On 7/6/12 4:33 PM, Alexander Hansen wrote:
> How "fairly soon" would you like it? I can go ahead and start branch_0_34.
>
> -- Alex
>
> On 7/6/12 7:16 AM, David R. Morrison wrote:
>> > Yes, I've been intending to do something like that.
>> >
>> > It would be very useful to have a release inclu
How "fairly soon" would you like it? I can go ahead and start branch_0_34.
-- Alex
On 7/6/12 7:16 AM, David R. Morrison wrote:
> Yes, I've been intending to do something like that.
>
> It would be very useful to have a release including 10.8 fairly soon, so that
> I could try out some postinst
Yes, I've been intending to do something like that.
It would be very useful to have a release including 10.8 fairly soon, so that I
could try out some postinstall.pl upgrade ideas with a fink-10.8.info file in
place in the distribution.
-- Dave
On Jul 6, 2012, at 8:04 AM, Alexander Hansen wr
And we'd probably want to have some way in the fink scripts to notify
users to install the bundle if they've upgrading their OS version. E.g.
maybe we could have postinstall.pl send a message when the current
Distribution value doesn't correspond to the current OS version.
On 7/6/12 6:59 AM, Davi
Good point. The reason this was done is documented in the perlXXX.info file,
but you are right that it creates potential upgrade problems.
I guess what we need is a package called perlXXX-upgrade which is a bundle that
depends on all these non-core pm's. Would that solve it, or am I overlookin
The VirtPackages.pm system-perl packages have extensive Provides lists of the
various -pmXXX packages. Apple supplies modules with its perl that are "extra",
not part of the upstream perl-core distro. The VP system-perl packages appear
to Provides these extra ones as well as the core ones. The r
