From: Sascha Kilian <sascha@sakisoft.de>
To: development@lists.ipfire.org
Subject: Re: Subversion (1.8.8)
Date: Fri, 14 Mar 2014 14:57:48 +0100 [thread overview]
Message-ID: <1394805468.2393.16.camel@localhost> (raw)
In-Reply-To: <1394802750.5059.4.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2615 bytes --]
Hi,
thanks for the Link.
Yes the syntax error is stay.
My Knowlege with Git is not good. I think i try to send you the Patches.
The base from my files you have :)
best regards from Germany
Sascha
Am Freitag, den 14.03.2014, 14:12 +0100 schrieb Michael Tremer:
> Hi,
>
> you can view the entire conversation over here:
>
> http://lists.ipfire.org/pipermail/development/2014-March/thread.html
>
> Do you still have trouble with the syntax error?
>
> If you are familiar with git, maybe you can upload your changes in a git
> repository on github or somewhere else, because this makes it a bit
> easier to keep track of the changes. Alternatively, you can post inline
> patches in these emails.
>
> -Michael
>
> On Fri, 2014-03-14 at 11:15 +0100, Sascha Kilian wrote:
> > Hi There,
> >
> > sry my Mailserver has a crash, can u send me the latest replys for
> > Subversion thread?
> >
> > Thanks
> >
> > Am Dienstag, den 11.03.2014, 11:01 +0100 schrieb Michael Tremer:
> > > Hi Sascha,
> > >
> > > thanks for your submission. I think we can include subversion, but there
> > > are some issues with this package:
> > >
> > > * The rootfile is missing.
> > >
> > > * You cannot use wget or something else that loads data from the
> > > internet, because you cannot be sure that it is online, that the file
> > > still exists on the server and it would be downloaded every time you
> > > build subversion. There are plenty of packages that have more than one
> > > source file. Please have a look at one of these and do it likewise.
> > >
> > > * You should probably use --prefix=/usr to install it to /usr (according
> > > to FHS).
> > >
> > > * I am not sure if subversion needs a lot of libraries to be fully
> > > functional like libneon for accessing repositories over http://. Did you
> > > check this? Those probably need to be included as well, so that
> > > subversion is actually usable.
> > >
> > > Best,
> > > -Michael
> > >
> > > On Mon, 2014-03-10 at 16:38 +0100, Sascha Kilian wrote:
> > > > Hi There,
> > > >
> > > > i want Subversion on my IPFire and i have created a LFS file for this.
> > > >
> > > > If it okay, please add it to the Repository.
> > > >
> > > > Best Regards
> > > >
> > > > Sascha
> > > > _______________________________________________
> > > > Development mailing list
> > > > Development(a)lists.ipfire.org
> > > > http://lists.ipfire.org/mailman/listinfo/development
> > >
> >
> >
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2014-03-14 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 15:38 Sascha Kilian
2014-03-11 10:01 ` Michael Tremer
2014-03-11 10:23 ` Sascha Kilian
2014-03-12 14:40 ` Sascha Kilian
2014-03-14 10:15 ` Sascha Kilian
2014-03-14 13:12 ` Michael Tremer
2014-03-14 13:57 ` Sascha Kilian [this message]
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=1394805468.2393.16.camel@localhost \
--to=sascha@sakisoft.de \
--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