Opened 9 years ago

Closed 9 years ago

#49082 closed update (wontfix)

OpenCoarrays @1.0.3 adding mpstats as dependency

Reported by: fanfarillo.gcc@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: OpenCoarrays

Description

Hi,

tracking users download is a very important statistics for our open source project. We would like to have mpstats as dependent library for OpenCoarrays. The attached patch should do the job.

Comments?

Cheers

Alessandro

Attachments (1)

Portfile-OpenCoarrays.diff (333 bytes) - added by fanfarillo.gcc@… 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by fanfarillo.gcc@…

Attachment: Portfile-OpenCoarrays.diff added

comment:1 Changed 9 years ago by pixilla (Bradley Giesbrecht)

Done in r140813.

Anyone with OpenCoarrays already installed will not pull in mpstats through this dependency until the OpenCoarrays version or revision increases. Should we increase the revision?

Last edited 9 years ago by pixilla (Bradley Giesbrecht) (previous) (diff)

comment:2 Changed 9 years ago by raimue (Rainer Müller)

Yes, the revision should have been increased when changing the list of dependencies. Please remember to include a reference to the ticket in the commit message for the record of maintainer approval.

We should not force users to install mpstats as its tracking is meant to be opt-in only. Please revert this change.

comment:3 in reply to:  2 ; Changed 9 years ago by pixilla (Bradley Giesbrecht)

Replying to raimue@…:

Yes, the revision should have been increased when changing the list of dependencies. Please remember to include a reference to the ticket in the commit message for the record of maintainer approval.

We should not force users to install mpstats as its tracking is meant to be opt-in only. Please revert this change.

Done in r140816

I'm surprised the mpstats port auto-activates reporting. There appears to be no way of fixing a situation like this where the ramifications of depending on mpstat was unknown. Wouldn't the mpstat port be safer if it required "port load mpstats"?

Last edited 9 years ago by pixilla (Bradley Giesbrecht) (previous) (diff)

comment:4 in reply to:  3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: wontfix
Status: newclosed

Replying to pixilla@…:

I'm surprised the mpstats port auto-activates reporting. There appears to be no way of fixing a situation like this where the ramifications of depending on mpstat was unknown. Wouldn't the mpstat port be safer if it required "port load mpstats"?

You could discuss that on the mailing list or open a new ticket.

Note: See TracTickets for help on using tickets.