Mail Archives: cygwin/2012/03/28/08:22:30
--------------enigF9FD5F1BAC59228C6F0E4C73
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 3/28/2012 20:09, Corinna Vinschen wrote:
> On Mar 28 18:39, JonY wrote:
>> On 3/28/2012 15:33, Corinna Vinschen wrote:
>>> On Mar 28 07:27, JonY wrote:
>>>> On 3/27/2012 16:36, Corinna Vinschen wrote:
>>>>> On Mar 26 22:59, Ryan Johnson wrote:
>>>>>> On 26/03/2012 9:40 PM, Jason Tishler wrote:
>>>>>>> New News:
>>>>>>> =3D=3D=3D =3D=3D=3D=3D
>>>>>>> I have updated the version of rebase to 4.1.0-1. The tarballs shou=
ld be
>>>>>>> available on a Cygwin mirror near you shortly.
>>>>>>>
>>>>>>> The following are the changes since the previous release:
>>>>>>>
>>>>>>> * Add rebase/rebaseall touch file (i.e., -t option) support.
>>>>>>>
>>>>>>> * Add rebaseall setup (i.e., -p option) support.
>>>>>>>
>>>>>>> * Add .oct to the default rebaseall suffix list.
>>>>>> I've been meaning to ask... but maybe the above-mentioned -p flag
>>>>>> obsoletes it now: What's the most efficient way to rebase after
>>>>>> running setup? We've had the rebase db for a while now, so running
>>>>>> rebaseall seems like overkill. Only the newly downloaded dlls need
>>>>>
>>>>> Now that the new rebase is out, I'm going to create an _autorebase
>>>>> package which will automatically call rebaseall at the end of a
>>>>> successful run of setup, if that run also updated existing DLLs or
>>>>> came with new DLLs.
>>>>
>>>> If I don't want it to run? I've never had any need to rebase DLLs on my
>>>> Win7 64bit machine.
>>>
>>> It doesn't hurt either.
>>>
>>>
>>
>> I hope it doesn't leave the system in an unusable state if some DLL is
>> still in use.
>>
>> I often have Cygwin processes running when I run setup to add new
>> packages, If any DLLs are in use, upgrade is postponed.
>=20
> The whole idea of the new rebase 4.1.0 was to allow to rebase all
> not-in-use DLLs and gracefully handle in-use DLLs by storing their
> location in the DB as well and arranging the not-in-use DLLs carefully
> around them.
>=20
> Go ahead, try it. If it doesn't work, complain here again. I wrote
> the aforementioned code; it's entirely my fault if something's broken.
>=20
>=20
> Corinna
>=20
Alright, will do so the next upgrade cycle.
--------------enigF9FD5F1BAC59228C6F0E4C73
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iEYEARECAAYFAk9zAhIACgkQp56AKe10wHffzgCfQ3i3FecOdIoPVw9CIbm0Viji
YE4An2Fbwymwfuwv2o6DfIxHvMmBA1PS
=SSGM
-----END PGP SIGNATURE-----
--------------enigF9FD5F1BAC59228C6F0E4C73--
- Raw text -