public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: development@lists.ipfire.org
Subject: Procedure to build missing packages from sources?
Date: Mon, 08 Jan 2018 00:23:36 -0500	[thread overview]
Message-ID: <CAH8yC8mbUmzVf0rFFAJyQP+Hw9ULjQJKK1dt5FF49wVzJhmNpQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

I'm trying to find the process or procedures to build missing programs
and packages from sources. For example, emacs is missing so I would
like to build it. I can build it locally on the IPfire or I can
[attempt to] cross-compile and scp it up to the IPfire.

My first question is, is there documentation that covers the topic? If
so, where is it?

My second question is, if there is no documentation, then what is the procedure?

My third question is, if it is not possible, then what are the
alternatives? Is there another way to get a missing program? Or should
we start looking for alternative firewalls? (I like IPfire and I
prefer to stay with it).

Thanks in advance.

Jeffrey Walton

             reply	other threads:[~2018-01-08  5:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  5:23 Jeffrey Walton [this message]
2018-01-08 10:24 ` Michael Tremer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH8yC8mbUmzVf0rFFAJyQP+Hw9ULjQJKK1dt5FF49wVzJhmNpQ@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=development@lists.ipfire.org \
    /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