Package: wnpp
Severity: wishlist
Owner: Nicholas D Steeves
Control: tag + moreinfo
Package name: emacs-wgrep
Version : 2.3.0
Upstream Author : Masahiro Hayashi
URL : https://github.com/mhayashi1120/Emacs-wgrep
License : GPL-3+
Programming Lang: Emacs LISP
Descript
Holger wrote:
>
>so at dc19 we came up with the idea of having a Debian event pre- or
>post-FOSDEM, an event like DebCamp or maybe a bug squashing party, so
>mostly self/unorganized.
>
>The only thing we would need is suitable room, and probably someone
>paying for it.
>
>And we'd need to agree on
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: ruby-unicode-utils
Version : 1.4.0
Upstream Author : Stefan Lang
* URL : http://github.com/lang/unicode_utils
* License : BSD-2-clause
Descript
Niko Tyni writes:
> It's not obvious to me what the ideal setup here should be, when there
> are no other reasons for such a dependency than 'need an implementation
> of the language the library is written in'.
I think there can be another reason: "needs a minimum version of the
interpreter langua
> On 17 Nov 2019, at 22:39, Niko Tyni wrote:
>
> - for PHP, there apparently used be a draft policy but it's gone with Alioth
> now.
> The remnants I could find [5] don't mention package dependencies. Looking at
> the
> archive, I see pretty much uniform dependencies on php-common, apparently
Hi,
at the last tech-ctte meeting the question came up of whether there's
a general rule in Debian about libraries/modules depending (or not)
on the corresponding interpreters for their implementation language.
It's not obvious to me what the ideal setup here should be, when there
are no other re
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin
* Package name: python-protego
Version : 0.1.15
Upstream Author : Anubhav Patel et al.
* URL : https://github.com/scrapy/protego
* License : BSD-3
Programming Lang: Python
Description : pure-Py
7 matches
Mail list logo