Hi,
On Sat, Jan 11, 2020 at 07:39:42PM +0100, Jose G. López wrote:
> I'm interested in packaging Julius [0], an open source re-implementation of
> Caesar III.
> As it requires the original assets (graphics, sounds, etc) from Caesar 3 to
> run I want to ask if it should go in contrib archive.
Hi!,
I'm interested in packaging Julius [0], an open source re-implementation of
Caesar III.
As it requires the original assets (graphics, sounds, etc) from Caesar 3 to run
I want to ask if it should go in contrib archive.
Another thing is it seems there's a RFP using the same name [1], what
On Sat, Jan 11, 2020 at 01:19:58PM +, David Griffith wrote:
> I think I've come up with what may be an ideal solution that lets me put the
> debian/ directory in the upstream. Please let me know what you think.
>
> deb:
> ifneq ($(and $(wildcard $(GIT_DIR)),$(shell which git)),)
>
On Sat, Jan 11, 2020 at 04:57:09AM +, David Griffith wrote:
> I'm trying to debianize Frotz 2.50 and put the debian/ directory into the
> git repository. A complication is that the contents of a dist file differs
> from what you get from a git clone.
You need to decide whether your Debian
Hello.
I could not agree more. Wearing those two hats can be
stressful sometimes.
In an ideal world I would be only developing, and would not
have to worry about the finer parts of each operating system
I am targeting.
Hence my two repositories: One for the project, one for the
packages. This
Your message dated Sat, 11 Jan 2020 15:50:29 +0100
with message-id <2020045029.gl12...@mapreri.org>
and subject line Re: Bug#948530: RFS: coinor-vol/1.5.4-1 [QA] -- Coin-or linear
programming solver
has caused the Debian Bug report #948530,
regarding RFS: coinor-vol/1.5.4-1 [QA] -- Coin-or
My reply is at the bottom. Please put your reply there too.
On Sat, 11 Jan 2020, David Given wrote:
I'd add that the recommended thing to do if you're trying to create a
package for software you own is to blatantly wear two hats: with one hat
you're the upstream author, and with the other hat
I'd add that the recommended thing to do if you're trying to create a
package for software you own is to blatantly wear two hats: with one hat
you're the upstream author, and with the other hat you're the packager.
Have two different repositories, don't add the debian/ directory to the
upstream
My reply is at the bottom. Please put your reply there too.
On Sat, 11 Jan 2020, Thomas Dettbarn wrote:
David Griffith hat am 11. Januar 2020 um 05:57 geschrieben:
I'm trying to debianize Frotz 2.50 and put the debian/ directory into the
git repository. A complication is that the contents
Hello David.
The way into debian is a complicated one. There are a LOT of
helper scripts out there, which have grown. Some of them are
still useful, some are not.
On top of that, the contents of the debian/ directory are
plentiful, and not very well documented, if I may say so.
My solution was
10 matches
Mail list logo
