Page MenuHomeFreeBSD

devel/libparserutils: update to 0.2.4
AbandonedPublic

Authored by fernape on Aug 30 2018, 5:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 18 2024, 1:14 PM
Unknown Object (File)
Jan 5 2024, 5:40 PM
Unknown Object (File)
Jan 4 2024, 12:52 AM
Unknown Object (File)
Nov 14 2023, 2:37 AM
Unknown Object (File)
Nov 8 2023, 3:03 PM
Unknown Object (File)
Oct 13 2023, 1:38 AM
Unknown Object (File)
Oct 7 2023, 1:54 PM
Unknown Object (File)
Jun 17 2023, 9:53 PM

Details

Reviewers
tcberner
tz
Summary

Reported by portscout

Bumping PORTREVISION for dependent ports

Test Plan
  • portlint -AC OK
  • poudriere builds for {10.4,11.1}{amd64,i386}, 12i386 OK
  • poudriere builds for dependent ports in {10.4,11.1}{amd64,i386} OK

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 19328
Build 18933: arc lint + arc unit

Event Timeline

devel/libparserutils/Makefile
25

Why +=?

Replace unnecessary += operator

I see no need to bump PORTREVISION for dependent ports.

I see no need to bump PORTREVISION for dependent ports.

.so library changes version:

in pkg-plist:

lib/libparserutils.so.%%VERSION%%
 # pkg info -l -F libparserutils-0.2.4.txz | grep so
        /usr/local/lib/libparserutils.so
        /usr/local/lib/libparserutils.so.0
        /usr/local/lib/libparserutils.so.0.2.4
root@10_4amd64-default:/wrkdirs/usr/ports/devel/libparserutils/work/pkg #

I see no need to bump PORTREVISION for dependent ports.

.so library changes version:

in pkg-plist:

lib/libparserutils.so.%%VERSION%%
 # pkg info -l -F libparserutils-0.2.4.txz | grep so
        /usr/local/lib/libparserutils.so
        /usr/local/lib/libparserutils.so.0
        /usr/local/lib/libparserutils.so.0.2.4
root@10_4amd64-default:/wrkdirs/usr/ports/devel/libparserutils/work/pkg #

If the shlib is changed (e.g. from libparserutils.so.0 to libparserutils.so.1), you'll have to bump PORTREVISION of dependent ports.
It tells everyone to "rebuild dependent ports" to link against the new one.

But not in this case.

No matter it is libparserutils.so.0.2.4 or libparserutils.so.0.20.40, the linker still uses /usr/local/lib/libparserutils.so.0 before and after this update.
Nothing is changed.
There's no need to bump/rebuild dependent ports.

I see no need to bump PORTREVISION for dependent ports.

.so library changes version:

in pkg-plist:

lib/libparserutils.so.%%VERSION%%
 # pkg info -l -F libparserutils-0.2.4.txz | grep so
        /usr/local/lib/libparserutils.so
        /usr/local/lib/libparserutils.so.0
        /usr/local/lib/libparserutils.so.0.2.4
root@10_4amd64-default:/wrkdirs/usr/ports/devel/libparserutils/work/pkg #

If the shlib is changed (e.g. from libparserutils.so.0 to libparserutils.so.1), you'll have to bump PORTREVISION of dependent ports.
It tells everyone to "rebuild dependent ports" to link against the new one.

But not in this case.

No matter it is libparserutils.so.0.2.4 or libparserutils.so.0.20.40, the linker still uses /usr/local/lib/libparserutils.so.0 before and after this update.
Nothing is changed.
There's no need to bump/rebuild dependent ports.

I might have misinterpreted the documentation then and being too enthusiastic bumping PORTREVISION I suppose.

Sorry for the rebuilding.

I see no need to bump PORTREVISION for dependent ports.

.so library changes version:

in pkg-plist:

lib/libparserutils.so.%%VERSION%%
 # pkg info -l -F libparserutils-0.2.4.txz | grep so
        /usr/local/lib/libparserutils.so
        /usr/local/lib/libparserutils.so.0
        /usr/local/lib/libparserutils.so.0.2.4
root@10_4amd64-default:/wrkdirs/usr/ports/devel/libparserutils/work/pkg #

If the shlib is changed (e.g. from libparserutils.so.0 to libparserutils.so.1), you'll have to bump PORTREVISION of dependent ports.
It tells everyone to "rebuild dependent ports" to link against the new one.

But not in this case.

No matter it is libparserutils.so.0.2.4 or libparserutils.so.0.20.40, the linker still uses /usr/local/lib/libparserutils.so.0 before and after this update.
Nothing is changed.
There's no need to bump/rebuild dependent ports.

I might have misinterpreted the documentation then and being too enthusiastic bumping PORTREVISION I suppose.

Sorry for the rebuilding.

A bump too much is better than one too few -- so keep that enthusiasm.

Sorry, @swills already updated it in the meantime in Ports r479003

Sorry, @swills already updated it in the meantime in Ports r479003

No worries. Thanks for the review though :-)