Re: FreeBSD Palemoon branding violation
@lbutlr writes: > Speaking with some experience it is nearly impossible to enforce > a ™ trademark, especially if there are other trademarks of the > word or phrase or name. If you want to use McDonald’s in your > name for a hardware store you better be sure you get a ® for it > if you want to defend it, since there is already an established ® > (more than one, in fact) in place. It is my understanding that - in the U.S. - trademarks are: 1) limited by industry. Apple Compuuter and Apple Corps (the Beatles' music label) got along just fine ... until Apple Compuuter started doing stuff with music on computers. More information on what followed is at: "https://en.wikipedia.org/wiki/Apple_Corps_v._Apple_Computer;. 2) limited by geography. Nudnik's Hardware, with one store outside Anchroage, will not be able to enforce trademark against Nudnik's Hardware one store im the U.S. Virgin Islands. McDonald's is obviously the case at the other end of that spectrum. 3) limited by prior usage. A "McDonald's" restaurant which has been in continuous operation in substantially the same location since 1867 may be able tell the other McDonald's to go whistle. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Vote: making wayland=on default
Yuri writes: > It appears that this is the case of fixing of something (xorg) > that wasn't/isn't broken in the first place. And if it is > considered broken, then how, in which way? You ask "Is it broken?". I ask "Is there a better way?" Think about gcc: it was developed in the mid '80s, and at the time was pretty dang impressive. But over time ... "provisional" hacks to handle less-common hardware or specific software anomalies became permanently entrenched (or so I am told) even as hardware changed, and both compiler technology and coding practices improved. I think of X the same way. To the list: I salute X for doing its job, but I have no brand loyalty. If something comes along that is some combination of a) more robust, b) faster, and c) as easy to install/manage I'll switch in a heartbeat. (Smaller footprint would be nice too.) Is that Wayland? Fact not (yet) in evidence. Is Wayland-on-FreeBSD in active development? If so: where - other than ports@ - do I go to check the /status quo/? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cython 0.14
blubee blubeeme writes: > I have a port that needs cython 0.14 and not cython 0.26 > > I tried all sorts of things but this; > BUILD_DEPENDS= cython=0.14:lang/cython3 > > always returns that cython 0.14 isn't found, cython 0.24 > is available but my port won't build with that version. > > How can I get cython 0.14? Does this work: USES=cython:0.14 ? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
