On 03/08/2017 11:33 PM, Adam Borowski wrote:
> I'd like to discuss (and then propose to -policy) the following rule:
>
> # Libraries which don't provide a convenient means of conditionally loading
> # at runtime (this includes most libraries for languages such as C), SHOULD
> # NOT declare a "Depe
On Wed, Mar 22, 2017 at 6:17 PM, Christian Seiler wrote:
> For $DAYJOB I had to work on Mac OS X a bit, and they have an interesting
> feature there: weakly binding to a shared library.
Apparently Solaris has support for optional shared libraries:
https://lists.debian.org/debian-devel/2015/02/ms
Hi,
now we have extensions disabled in Chromium by default. If I did my
homeworks correctly, that prevents Chromium from phoning home by
default, and prevents a previous scenario where extensions could be
installed but not upgraded, becoming security issues over time.
Now, suppose I need an exten
On 22 March 2017 at 12:03, Enrico Zini wrote:
> Hi,
>
> now we have extensions disabled in Chromium by default. If I did my
> homeworks correctly, that prevents Chromium from phoning home by
> default, and prevents a previous scenario where extensions could be
> installed but not upgraded, becomin
Package: wnpp
Severity: wishlist
Owner: Rhonda D'Vine
* Package name: sassphp
Version : 0.5.10
Upstream Author : Jamie Rumbelow
* URL : https://github.com/absalomedia/sassphp
* License : MIT
Programming Lang: PHP
Description : PHP bindings to libsass -
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: pktanon
Version : 1.4.0-dev
Upstream Author : Christoph P. Mayer, Thomas Gamer, Marcus Schöller
* URL : http://www.tm.uka.de/software/pktanon/index.html
* License : GPLv3
Programming Lan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey Enrico
On 22/03/2017 13:03, Enrico Zini wrote:
> Now, suppose I need an extension, what is the proper way to have it in
> Debian, so that it gets upgraded when needed? With that proper way, wh
at
> amount of phoning home is going to happen?
See
On Wed, Mar 22, 2017 at 08:16:14PM +0200, Jonathan Carter (highvoltage) wrote:
> so what's going to be the best way to make these
> available to Debian stable users?
https://wiki.debian.org/Chromium#Extensions
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Mar 22, 2017 at 11:41:16PM +0500, Andrey Rahmatullin wrote:
> On Wed, Mar 22, 2017 at 08:16:14PM +0200, Jonathan Carter (highvoltage) wrote:
> > so what's going to be the best way to make these
> > available to Debian stable users?
> https://wiki.debian.org/Chromium#Extensions
Thanks, tha
On Wed, Mar 22, 2017 at 08:16:14PM +0200, Jonathan Carter (highvoltage) wrote:
> I'm taking a look at https://github.com/gorhill/uBlock since it's gpl-3
> and has proper releases (I would expect that a lot of chromium
> extensions are a licensing nightmare).
Note that this source package is alread
At Wed, 22 Mar 2017 12:03:02 +0100,
Enrico Zini wrote:
> now we have extensions disabled in Chromium by default. If I did my
> homeworks correctly, that prevents Chromium from phoning home by
> default, and prevents a previous scenario where extensions could be
> installed but not upgraded, becomin
Package: wnpp
Severity: wishlist
Owner: Sanford Rockowitz
* Package name: ddcutil
Version : 0.7.3
Upstream Author : Sanford Rockowitz
* URL : http://www.ddcutil.com
* License : GPL
Programming Lang: C
Description : control monitor settings
ddcutil is
On Wed, Mar 22, 2017 at 01:58:20PM -0700, Sean Whitton wrote:
> On Wed, Mar 22, 2017 at 08:16:14PM +0200, Jonathan Carter (highvoltage) wrote:
> > I'm taking a look at https://github.com/gorhill/uBlock since it's gpl-3
> > and has proper releases (I would expect that a lot of chromium
> > extension
On Wed, Mar 22, 2017 at 09:51:12PM +0100, Jeroen Dekkers wrote:
> If we already know this is going to be major issue, why aren't we
> doing the sensible thing and enable extensions by default
The story of extensions in Debian Chromium is a strange and sad one.
See also https://bugs.debian.org/cgi-b
On Wed, Mar 22, 2017 at 10:48:28PM -0400, James McCoy wrote:
> #858526 has an attempt to produce a binary package for Chromium. I've
> never touched browser extensions before, so extra eyes would be nice,
> but it seems to work.
Certainly well enough to be uploaded to experimental -- it's in NEW.
On Wed, 22 Mar 2017 04:50:38 -0700 Jose R R said:
> On Tue, Mar 21, 2017 at 4:55 PM, Ross Vandegrift wrote:
> [...]
> > Oh I see - I misunderstood your previous message and thought you were
> > targeting sid. You need to backport + rebuild for jessie. IIRC, the
> > only change I needed was to
16 matches
Mail list logo
