Summary: | Mk/Uses/python.mk Prevent checksum mismatches for compiled python files on installing python ports via the ports tree | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Marcus von Appen <mva> | ||||
Component: | Ports Framework | Assignee: | freebsd-python (Nobody) <python> | ||||
Status: | In Progress --- | ||||||
Severity: | Affects Only Me | CC: | portmgr | ||||
Priority: | Normal | Keywords: | needs-qa | ||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Marcus von Appen
2012-06-03 16:00:26 UTC
Responsible Changed From-To: freebsd-ports-bugs->freebsd-python Python pr Responsible Changed From-To: freebsd-python->portmgr Over to portmgr, since bsd.port.mk is portmgr territory. An exp-run will be needed to ensure that nothing breaks. Is this still valid? -- Regards, Bryan Drewery On, Wed Oct 09, 2013, Bryan Drewery wrote:
> Is this still valid?
Yes. The problem still exists.
Cheers
Marcus
On 10/10/2013 12:45 AM, Marcus von Appen wrote:
> On, Wed Oct 09, 2013, Bryan Drewery wrote:
>
>> Is this still valid?
>
> Yes. The problem still exists.
Right, but is the PATCH still valid and sufficient? I recall some effort
to fix this previously.
--
Regards,
Bryan Drewery
Bryan Drewery <bdrewery@freebsd.org>: > On 10/10/2013 12:45 AM, Marcus von Appen wrote: >> On, Wed Oct 09, 2013, Bryan Drewery wrote: >> >>> Is this still valid? >> >> Yes. The problem still exists. > > Right, but is the PATCH still valid and sufficient? I recall some effort > to fix this previously. I need to check, if the patch still cleanly applies (I doubt that) and I am not satisfied with its hackish approach. A cleaner way (e.g. with an internal plist-post-cleanup: hook) would be nice, so it can be reused multiple times throughout different .mk files and (maybe) even used by some ports, which might create variable content files, that could create checksum mismatches. Would such a hook be desirable for portmgr or should this exist (for now) as a python-specific hack? In either case, I'll recheck and update the patch. Cheers Marcus Responsible Changed From-To: portmgr->freebsd-python Back to python@, we should evaluate the patch once more before doing anything Is this bug still relevant? Yes Canonicalise python@ assignment. |