Summary: | new port: misc/heyu2 for X10 control | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | mstowe | ||||
Component: | Individual Port(s) | Assignee: | Oliver Lehmann <oliver> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | ||||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
mstowe
2004-03-29 17:20:07 UTC
State Changed From-To: open->feedback Is this a successor of misc/heyu port? Is it worth separate port or should we update existing misc/heyu port? Is there a reason to have heyu 1 and heyu 2 alongside in ports tree? > Is this a successor of misc/heyu port? Is it worth > separate port or should we update existing misc/heyu port? > Is there a reason to have heyu 1 and heyu 2 alongside > in ports tree? Well, they're separate branches, and the heyu2 branch has been fairly unstable -- but also, the file names are different, and the setup files are very different. They can both coexist on a system, though they can't both control the same device. I'd be inclined to think of them like php3/php4, but I don't feel particularly strongly about it. State Changed From-To: feedback->open Feedback received a while ago. Responsible Changed From-To: freebsd-ports-bugs->oliver I'll take care State Changed From-To: open->repocopy please copy misc/heyu to misc/heyu2 Responsible Changed From-To: oliver->portmgr please copy misc/heyu to misc/heyu2 State Changed From-To: repocopy->open Repocopy completed. Responsible Changed From-To: portmgr->oliver Repocopy completed. State Changed From-To: open->closed Committed, Thanks |