perl ports overwriting files, so need -f?
Caspar Florian Ebeling
febeling at macports.org
Fri Sep 12 15:41:48 PDT 2008
On Fri, Sep 12, 2008 at 11:48 PM, Vincent Lefevre
<vincent-opdarw at vinc17.org> wrote:
> On 2008-09-12 11:43:06 -0400, Daniel J. Luke wrote:
>> On Sep 12, 2008, at 8:53 AM, Vincent Lefevre wrote:
>>> On 2008-09-12 14:45:28 +0200, Caspar Florian Ebeling wrote:
>>>> On Fri, Sep 12, 2008 at 2:42 PM, Vincent Lefevre
>>>> <vincent-opdarw at vinc17.org> wrote:
>>>>> On 2008-09-12 13:00:53 +0200, Caspar Florian Ebeling wrote:
>>>>>> Do I get it right that one has to force a good part
>>>>>> of the perl ports to make them install?
>>>>> It's better not to install them.
>>>> What about ports which depend on perl ports?
>>> In general, there is no reason to depend on such ports.
>> please stop trolling.
> You are annoying. I'm just saying that this can be a bug. This
> is based on real experience: On ***every*** port I've tried that
> depends on such a module, I've installed a local version without
> the dependency (thus, keeping the modules from perl 5.8) and had
> no problems at all. The bugs I've reported have been fixed.
> So, the user should try without the dependency and see if it is
> needed or not, and report a bug.
I removed the deps as well and my script still works, so
this might be true. The two suspects I know of now are test-harness
and test-simple, so that might be only unit test related anyway.
Which other ports do this stupid thing, btw? Should they
maybe removed entirely?
florian.ebeling at gmail.com
More information about the macports-users