Package: sponsorship-requests
Severity: wishlist
Hey dear mentors!
I'm looking for a sponsor for my package "libretro-beetle-vb"
This is the libretro port of Beetle/Mednafen VB module, a
Virtual Boy emulator.
It's a fork of Mednafen to fit better with the libretro API, so it's
not possible to
On Mon, Apr 11, 2016 at 7:22 AM, Matthew Tytel wrote:
> Thanks for the review.. sigh... A lot to do.
>
> I could use a little guidance though. I'm using this library called JUCE:
> https://www.juce.com/
> https://github.com/julianstorer/JUCE
>
> It looks like a lot of the problems are stemming from
Let's make it clear here.
Only EkeEke can change the license of Genesis Plus GX. It does not
matter if MAME is GPL or whatever now. It's a derivative work on OLD
code which is non-commercial.
And please don't flood here...
sergio-br2
On Thu, 7 Apr 2016 10:03:54 -0430 PICCORO McKAY Lenz
w
Package: sponsorship-requests
Severity: wishlist
Hey dear mentors!
I'm looking for a sponsor for my package "libretro-beetle-psx"
This is the libretro port of Beetle PSX, a fork of Mednafen PSX,
which is very accurate and has very good support for the Sony
PlayStation commercial games.
* Pack
Package: sponsorship-requests
Severity: wishlist
Hey dear mentors!
I'm looking for a sponsor for my package "libretro-gambatte"
This is the libretro port of Gambatte.
Gambatte is a portable, open-source Game Boy and Game Boy Color
emulator, focused on accuracy.
* Package name : libretro
Package: sponsorship-requests
Severity: wishlist
Hey dear mentors!
I'm looking for a sponsor for my package "libretro-snes9x"
This is the libretro port of Snes9x.
Snes9x is a cross platform SNES emulator, fast and it has a good
compatibility with commercial games.
The code diverge from Snes9x
Thanks for the review.. sigh... A lot to do.
I could use a little guidance though. I'm using this library called JUCE:
https://www.juce.com/
https://github.com/julianstorer/JUCE
It looks like a lot of the problems are stemming from that project.
And, it's a little big and unfamiliar to take on in
+++ Jakub Wilk [2016-04-10 17:15 +0200]:
> * Wookey , 2016-04-10, 15:49:
> >>nmh installs it's binaries (~20) into /usr/bin/nmh.
>
> Actually it installs to /usr/bin/mh, ...
>
> >>Now I try to do the same, and install mmh's binaries into /usr/bin/mmh,
> >>but Lintian complain about FHS violation.
On Sun, Apr 10, 2016 at 07:20:50PM +0200, Tomasz Buchert wrote:
> > ] Architecture: amd64 arm64 ppc64el s390x
> >
> > But why would you artificially restrict this to just these?
> >
> > 2.0.3-1 successfully built also on:
> > alpha kfreebsd-amd64 mips64el ppc64 sparc64 x32
> >
> > Of these, only
On 10/04/16 18:53, Adam Borowski wrote:
> On Sun, Apr 10, 2016 at 05:52:29PM +0200, Tomasz Buchert wrote:
> > On 09/04/16 18:31, Andreas Tille wrote:
> > > On Sat, Apr 09, 2016 at 04:47:35PM +0200, Tomasz Buchert wrote:
> > > > the only reason is that it doesn't build on most architectures. The
> >
On Sun, Apr 10, 2016 at 05:52:29PM +0200, Tomasz Buchert wrote:
> On 09/04/16 18:31, Andreas Tille wrote:
> > On Sat, Apr 09, 2016 at 04:47:35PM +0200, Tomasz Buchert wrote:
> > > the only reason is that it doesn't build on most architectures. The
> > > upstream devel version build, I think, on oth
Wookey writes:
> +++ Dmitry Bogatov [2016-04-10 08:34 +0300]:
>> nmh installs it's binaries (~20) into /usr/bin/nmh. Now I try to
>> do the same, and install mmh's binaries into /usr/bin/mmh, but
>> Lintian complain about FHS violation. The only allowed
>> subdir of /usr/bin is /usr/bin/mh.
> So
On 09/04/16 18:31, Andreas Tille wrote:
> Hi Tomasz,
>
> On Sat, Apr 09, 2016 at 04:47:35PM +0200, Tomasz Buchert wrote:
> >
> > the only reason is that it doesn't build on most architectures. The
> > upstream devel version build, I think, on other archs, but it hasn't
> > been released yet. I've
* Wookey , 2016-04-10, 15:49:
nmh installs it's binaries (~20) into /usr/bin/nmh.
Actually it installs to /usr/bin/mh, ...
Now I try to do the same, and install mmh's binaries into
/usr/bin/mmh, but Lintian complain about FHS violation. The only
allowed subdir of /usr/bin is /usr/bin/mh.
S
Hey G.
Copyright is updated.
> debian packaging should be GPL-2+ and not GPL-3+, otherwise you might
> not be able to forward patches back in GPL-2+ mode.
Changed that.
> debian/install with an sh script inside is something that worries me
a little
> bit (even if possible)
>
> can't you ple
+++ Dmitry Bogatov [2016-04-10 08:34 +0300]:
>
> [CC nmh maintainer]
>
> Hello!
>
> I am packaging mmh (http://marmaro.de/prog/mmh), which is fork of
> nmh. Both of them are mail user agents.
>
> nmh installs it's binaries (~20) into /usr/bin/nmh. Now I try to
> do the same, and install mmh's b
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "engauge-digitizer":
* Package name: engauge-digitizer
Version : 7.2-1
Upstream Author : Mark Mitchell
* URL : https://github.com/markummitchell/engauge6
* Lic
Thanks to all who answered my questions.
So, to summarize (and ensure I understood all answers correctly):
- For packages which don't have intermediate files (things that don't
need to be built, like scripts, static data, configuration files, or
whatever), it's perfectly fine to have a single ups
18 matches
Mail list logo
