Page MenuHomeFreeBSD

libcasper: Move everything to the libcasper package
ClosedPublic

Authored by ivy on Tue, Nov 4, 7:04 AM.
Tags
None
Referenced Files
F134845130: D53576.id.diff
Tue, Nov 4, 9:09 PM
F134813356: D53576.id165796.diff
Tue, Nov 4, 6:32 PM
F134768480: D53576.diff
Tue, Nov 4, 12:37 PM
F134768470: D53576.diff
Tue, Nov 4, 12:37 PM
F134763673: D53576.id.diff
Tue, Nov 4, 11:50 AM
F134751624: D53576.diff
Tue, Nov 4, 9:29 AM
Subscribers

Details

Summary

The libcasper package exists to contain libcasper, but for some reason,
only the libcap_net service was in the package, with libcasper itself
and the rest of the services being in runtime. Move everything to the
libcasper package, except tests, which stay in the tests package.

MFC after: 1 day

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ivy requested review of this revision.Tue, Nov 4, 7:04 AM

AFAICT what happened is:

  • the casper services mostly predate the introduction of pkgbase packages, and ended up in runtime
  • @oshogbo added cap_net and (reasonably) put it in a libcasper package but other services were not moved
  • cap_netdb was added, probably with a Makefile copied from some other existing service

Will runtime need a dependency on libcasper now?

Will runtime need a dependency on libcasper now?

yes, since several things in runtime use libcasper, but i don't think that's an issue: runtime already has several similar shlib dependencies.

This revision is now accepted and ready to land.Wed, Nov 5, 12:19 AM