From: ng0 <contact.ng0@cryptolab.net>
To: Mekeor Melire <mekeor.melire@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Package request: fortune
Date: Wed, 15 Feb 2017 19:35:20 +0000 [thread overview]
Message-ID: <20170215193520.tlqqyjbk2s6lzamd@wasp> (raw)
In-Reply-To: <20170215193844.0de1ab69@gmail.com>
On 17-02-15 19:38:44, Mekeor Melire wrote:
> Am Wed, 15 Feb 2017 13:37:55 +0000
> schrieb ng0 <contact.ng0@cryptolab.net>:
>
> > On 17-02-14 21:24:06, Caleb Herbert wrote:
> > > Could someone make a package for fortune?
> > >
> >
> > This looks like a very quick task (for me). Do you need help with
> > packaging this and want someones guidance? Otherwise I'd say you could
> > take other distros packages as inspiration/starting point. For example
> > archlinux: https://www.archlinux.org/packages/community/x86_64/fortune-mod/
>
>
> The official repository isn't directly available anymore because http://www.redellipse.net/code/fortune is down.
Oh, so it wasn't just me.
> We could use this maintained repository of fortune-mod on GitHub:
> https://github.com/shlomif/fortune-mod
I'd prefer this github, or debian without patches applied.
> Or we could use the latest official release, hosted by Arch or Debian.
> https://sources.archlinux.org/other/fortune-mod/
> http://ftp.de.debian.org/debian/pool/main/f/fortune-mod/
>
> It might also help to look into the Nix package definition, by the way:
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/fortune/default.nix
>
> If nobody wants to do this, I could probably create a package for this next week.
>
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-02-15 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 3:24 Package request: fortune Caleb Herbert
2017-02-15 13:37 ` ng0
2017-02-15 18:38 ` Mekeor Melire
2017-02-15 19:35 ` ng0 [this message]
[not found] ` <b6a69627-9d7d-b331-58e3-9220177d077f@bluehome.net>
[not found] ` <20170215215259.ytztxobsz7enutej@wasp>
[not found] ` <7ca8b418-06cc-4c2b-116a-d2f418699c46@bluehome.net>
[not found] ` <20170216092722.bdmjaikj4nutgxo4@wasp>
[not found] ` <8e80e065-ecf9-a7b3-afb9-4889a9cd60c0@bluehome.net>
2017-02-17 19:35 ` ng0
2017-02-19 3:15 ` Caleb Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170215193520.tlqqyjbk2s6lzamd@wasp \
--to=contact.ng0@cryptolab.net \
--cc=help-guix@gnu.org \
--cc=mekeor.melire@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).