Groups > linux.debian.user > #201430

Re: basilisk-browser

From	Reco <recoverym4n@enotuniq.net>
Newsgroups	linux.debian.user
Subject	Re: basilisk-browser
Date	2018-10-19 12:30 +0200
Message-ID	<wKAcx-1Cb-3@gated-at.bofh.it> (permalink)
References	(2 earlier) <wKcjU-3Na-9@gated-at.bofh.it> <wKq3v-3WX-1@gated-at.bofh.it> <wKwBY-7Sd-17@gated-at.bofh.it> <wKwVj-7Yp-3@gated-at.bofh.it> <wKxom-8mH-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

	Hi.

On Fri, Oct 19, 2018 at 08:26:20AM +0100, mick crane wrote:
> On 2018-10-19 07:58, Dominik George wrote:
> > > > > [1] https://github.com/jasperla/openbsd-wip/issues/86
> > 
> > Seriously? They forbid linking against libraries if their code is not
> > shipped with their sources?
> > 
> > That also seems like a security nightmare in the making.
> > 
> > Mozilla themselves weren't even *that* ridiculous, were they?
> > 
> 
> I'm not understanding what "Official branding" refers to in that exchange.
> If anyone has the time to explain.

It's the same as Mozilla's branding - [1].
Either you build the software the way upstream wants, or you lose the
right to call resulting software its official name (Palemoon in this
case).
Debian project was able to negotiate this with Mozilla some years ago.
In the case of Palemoon - well, OpenBSD project won't a Palemoon port in
a foreseable future.

Reco

[1] https://lwn.net/Articles/676799/

Thread

basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 09:40 +0200
  Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 10:10 +0200
    Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 11:00 +0200
      Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 11:20 +0200
        Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-18 14:50 +0200
          Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 16:40 +0200
            Re: basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 17:00 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 17:10 +0200
        Re: basilisk-browser John Crawley <john@bunsenlabs.org> - 2018-10-19 03:00 +0200
      Re: basilisk-browser Doug <dmcgarrett@optonline.net> - 2018-10-19 01:40 +0200
        Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-19 06:30 +0200
          Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:40 +0200
        Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 08:40 +0200
          Re: basilisk-browser Dominik George <natureshadow@debian.org> - 2018-10-19 09:00 +0200
            Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 09:30 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 12:30 +0200
                Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 13:10 +0200
              Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:50 +0200
            Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 11:30 +0200
              Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-19 15:40 +0200
            Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-20 04:20 +0200
              Re: basilisk-browser fmneto@fmneto.com.br - 2018-10-20 05:00 +0200
                Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-20 14:00 +0200

csiph-web