Date: Sat, 06 Feb 2010 09:55:19 +0000 From: Matthew Seaman <m.seaman@black-earth.co.uk> To: Dominic Fandrey <kamikaze@bsdforen.de> Cc: freebsd-ports@freebsd.org Subject: Re: CONFLICTS checks during the wrong stage Message-ID: <4B6D3C87.3020608@black-earth.co.uk> In-Reply-To: <4B6D382B.7080405@bsdforen.de> References: <4B6D382B.7080405@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAA8DD67AD4E9AA47293FAFF9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 06/02/2010 09:36, Dominic Fandrey wrote: > It appears CONFLICTS is checked before build instead of checking > it before install. Why? >=20 > # portmaster -Do lang/perl5.10 lang/perl5.8 >=20 > =3D=3D=3D>>> Currently installed version: perl-threaded-5.8.9_3 > =3D=3D=3D>>> Port directory: /usr/ports/lang/perl5.10 > =3D=3D=3D>>> Launching 'make checksum' for lang/perl5.10 in background > =3D=3D=3D>>> Gathering dependency list for lang/perl5.10 from ports > =3D=3D=3D>>> No dependencies for lang/perl5.10 =20 >=20 > =3D=3D=3D>>> Starting build for lang/perl5.10 <<<=3D=3D=3D >=20 > =3D=3D=3D>>> All dependencies are up to date >=20 > =3D=3D=3D> Cleaning for perl-threaded-5.10.1 >=20 >=20 > =3D=3D=3D> perl-threaded-5.10.1 conflicts with installed package(s):=20 > perl-threaded-5.8.9_3 >=20 > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 >=20 > Stop in /usr/ports/lang/perl5.10. >=20 > =3D=3D=3D>>> make failed for lang/perl5.10 > =3D=3D=3D>>> Aborting update There was a discussion about this over on questions recently, starting he= re: http://lists.freebsd.org/pipermail/freebsd-questions/2010-January/211053.= html Lots of people are less than completely satisfied with the change. The whole argument boils down to: * Having to jump through extra hoops in order to do some perfectly reasonable operations such as portupgrade -o new/port -f old/port-it-conflicts-with versus: * Accidentally spending a long time compiling a port when a conflicting port is already installed. Personally I feel that this change is in error -- it's ticking off the vast majority of people that manage their ports day-to-day for the sake of avoiding some newbie errors that you'ld only tend to make once or twice. Printing out great big warnings at fetch and compile time when a conflict is detected seems a much more reasonable response. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard, Flat 3 Black Earth Consulting Ramsgate Kent, CT11 9PW Free and Open Source Solutions Tel: +44 (0)1843 580647 --------------enigAA8DD67AD4E9AA47293FAFF9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkttPI4ACgkQ8Mjk52CukIyp5gCfeo/NJC0U70+ja6FF5v4/8WZO 4vEAniGoqYM6ZZzpFBe0L7AIwl+npHDp =//7J -----END PGP SIGNATURE----- --------------enigAA8DD67AD4E9AA47293FAFF9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B6D3C87.3020608>