* Procedure to build missing packages from sources?
@ 2018-01-08 5:23 Jeffrey Walton
2018-01-08 10:24 ` Michael Tremer
0 siblings, 1 reply; 2+ messages in thread
From: Jeffrey Walton @ 2018-01-08 5:23 UTC (permalink / raw)
To: development
[-- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Procedure to build missing packages from sources?
2018-01-08 5:23 Procedure to build missing packages from sources? Jeffrey Walton
@ 2018-01-08 10:24 ` Michael Tremer
0 siblings, 0 replies; 2+ messages in thread
From: Michael Tremer @ 2018-01-08 10:24 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Hello,
there is documentation on how to build IPFire and add new packages:
On Mon, 2018-01-08 at 00:23 -0500, Jeffrey Walton wrote:
> 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?
Here is how to build the entire distribution:
https://wiki.ipfire.org/devel/ipfire-2.x/build-howto
Here is how to add a new package:
https://wiki.ipfire.org/devel/ipfire-2.x/addon-howto
I guess the latter one is not written too end-user friendly, but of course you
can ask questions here and improve anything that you think might be helpful to
other developers.
If you are done with everything and you have tested (ideally by other people as
well) your new package and it should be part of the distribution, here is how to
submit patches:
https://wiki.ipfire.org/devel/submit-patches
> 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).
No, definitely stay with us :)
>
> Thanks in advance.
>
> Jeffrey Walton
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-01-08 10:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-08 5:23 Procedure to build missing packages from sources? Jeffrey Walton
2018-01-08 10:24 ` Michael Tremer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox