From: Ghislain Hachey <ghachey.lists@gmail.com>
To: development@lists.ipfire.org
Subject: Re: IPFire Building Packages
Date: Mon, 07 Jul 2014 17:50:49 +0800 [thread overview]
Message-ID: <53BA6D79.2070900@gmail.com> (raw)
In-Reply-To: <1404724962.19419.19.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On 7/7/14, 17:22, Michael Tremer wrote:
> Are you sure that subversion needs apr at runtime? It certainly needs
> the library, but I think that everything that is needed by subversion at
> runtime should be in the core system already.
>
> We had a subversion package which was dropped in 2008, because the
> IPFire project switched to git and there was no one who wanted to
> maintain subversion any more.
>
> http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=a91ca65e82da80139f0e0675def755561ec7d478
>
>> >Long story, but I'm curious about why apache makes used of bundled third
>> >party sources here, is this a special case that requires to go against
>> >what's encouraged?
> APR is a part of apache. Some distributions simply create a subpackage
> for apr as it is usually not needed at runtime, just for development.
>
OK, that all makes sense. So I might as well just point the subversion
./configure script to use the ones in httpd sources for the build and be
done with it. I don't mind maintaining the package (and other orphan
packages that I may want to use from time to time). What does this
usually entail? Just following the upstream project for bug and security
fixes and re-building new sources when that happens?
--
GH
next prev parent reply other threads:[~2014-07-07 9:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 9:45 Ghislain Hachey
2014-07-05 14:15 ` Michael Tremer
2014-07-05 23:01 ` Ghislain Hachey
2014-07-06 8:57 ` Michael Tremer
2014-07-06 9:44 ` Ghislain Hachey
2014-07-07 9:18 ` Michael Tremer
2014-07-08 10:35 ` MySQL 5.6.19 Sascha Kilian
2014-07-08 13:10 ` Sascha Kilian
2014-07-29 8:13 ` LuaJIT Panic on IPFire Ghislain Hachey
2014-07-29 8:27 ` Arne Fitzenreiter
2014-07-07 8:49 ` IPFire Building Packages Ghislain Hachey
2014-07-07 9:22 ` Michael Tremer
2014-07-07 9:50 ` Ghislain Hachey [this message]
2014-07-07 10:35 ` Michael Tremer
2014-07-07 10:48 ` Ghislain Hachey
2014-07-11 4:18 ` Ghislain Hachey
2014-07-06 8:51 ` Ghislain Hachey
2014-07-06 9:03 ` 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=53BA6D79.2070900@gmail.com \
--to=ghachey.lists@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