Page MenuHomeFreeBSD

Flavorize tor-devel
AbandonedPublic

Authored by yuri on Jun 26 2018, 6:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Sep 30, 9:59 PM
Unknown Object (File)
Tue, Sep 29, 2:42 PM
Unknown Object (File)
Tue, Sep 8, 12:51 PM
Unknown Object (File)
Sep 5 2026, 10:32 AM
Unknown Object (File)
Sep 4 2026, 10:24 PM
Unknown Object (File)
Sep 3 2026, 4:44 PM
Unknown Object (File)
Sep 3 2026, 12:13 PM
Unknown Object (File)
Sep 1 2026, 4:31 PM

Details

Reviewers
None
Summary

security/tor-devel is develed in favor or tor@devel

Diff Detail

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

Event Timeline

Mat,

CONFLICTS_INSTALL doesn't work with this port now.
When tor-devel is installed from the previous package, make fails because of the conflict error.
But when tor-devel is installed from this port with make FLAVOR=dev install, make doesn't fail any more.

The code checking CONFLICTS_INSTALL depends on the origin, this seems to be wrong.

Yuri

tcberner added inline comments.
security/tor/Makefile
20

^ wouldn't devel (given the resulting pkg name) or even alpha be more appropriate instead of dev?

No.

A single port origin should produce a single version. Make this a slave port if you want, but do not mix more than one version in one port.

yuri added inline comments.
security/tor/Makefile
20

Tobias,

there is a convention that development versions are called with dev suffix. Many people know this, for example, in linux such packages are always called -dev. I mostly named it this way for this reason.

security/tor/Makefile
20

In some other dimension, maybe. In the ports tree, on the other hand:

$ ls -l -d */*-devel|wc -l
     115
$ ls -l -d */*-dev|wc -l
ls: */*-dev: No such file or directory
       0

Please do not invent conventions, or forcefully try to import them from some other part of the universe.