Page MenuHomeFreeBSD

Remove the FreeBSD 10 hack
AbandonedPublic

Authored by bapt on Oct 2 2014, 12:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 9, 3:11 AM
Unknown Object (File)
Dec 19 2023, 9:31 PM
Unknown Object (File)
Nov 4 2023, 6:49 AM
Unknown Object (File)
Oct 3 2023, 6:41 AM
Unknown Object (File)
Jul 25 2023, 1:58 AM
Unknown Object (File)
Apr 25 2017, 6:39 AM
Unknown Object (File)
Apr 12 2017, 11:23 PM
Unknown Object (File)
Mar 31 2017, 10:30 AM
Subscribers

Details

Reviewers
tijl
bdrewery
Group Reviewers
portmgr
Summary

The huge libtool work that have past should have fixed the situation
It might be interesting to get exp-run with that patch (on freebsd 10)
to see what happen

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bapt retitled this revision from to Remove the FreeBSD 10 hack.
bapt updated this object.
bapt edited the test plan for this revision. (Show Details)
bapt added a reviewer: portmgr.
antoine added a subscriber: antoine.

I will exp-run this after PR 194068 is committed.

USES=libtool doesn't patch this and config.rpath is gettext related, so I don't think you can remove this yet. Maybe it's possible to move this to a USES=fbsd10fix.

I want to first see how many things are inpacted now

Currently the message printed by the fix (===> FreeBSD 10 autotools fix applied to...) is always shown even if there are no changes to a file. If it were only shown if file and file.fbsd10bak are different (using "cmp -s"?) it would be easier to find out which ports still need it.

bdrewery requested changes to this revision.Oct 7 2014, 3:11 PM
bdrewery added a reviewer: bdrewery.
bdrewery added a subscriber: bdrewery.

Please include a CHANGES entry on how to fix ports that fail due to not having this. It is needed for vendors and people who maintain custom trees.

This revision now requires changes to proceed.Oct 7 2014, 3:11 PM