From: "Filip Gruszczyński" <gruszczy@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: archfs - filesystem for rdiff-backup archives
Date: Fri, 3 Aug 2007 09:25:53 +0000 [thread overview]
Message-ID: <1be78d220708030225o6d70b717mbe6e26b4e8d7e46c@mail.gmail.com> (raw)
In-Reply-To: <f8tsoc$gb0$1@sea.gmane.org>
> Er it's been pointed out to me that this is a Google SoC project, so
> apologies for the beginners info. (I'd forgotten your earlier post.)
Oh, no problem, I am a beginner after all :-) And I always forget to
add project's homepage
to the message :-/
> BTW I don't recommend autotools (there's a reason they're called autohell ;)
Yeah, now I know that myself ;-)
> especially if you're not writing from scratch. (That's why you get all
> those redundant configure checks..) A simple system.mk which gets included
> in the makefile is a lot easier for everyone. ion3 (which is now in mabi's
> overlay iirc) does this, and it's a doddle to configure. (I think it was
> one or two sed calls.)
Well, you are third person, that is telling me that (though you all
differ with alternative tools - from CMake, to pkg-config, to what you
are suggesting now). If only I knew it, when I was getting down to it.
Unfortunately, my lack of experience doesn't make this project any
easier, it's my first 3 months, that I'm doing anything like this.
However, for the time being I will stick to what I could create with
those autotools - I get shivers, when I imagine, that I have to learn
something like this again ;-)
--
Filip Gruszczyński
prev parent reply other threads:[~2007-08-03 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 21:48 [gentoo-dev] archfs - filesystem for rdiff-backup archives Filip Gruszczyński
2007-08-02 19:47 ` Filip Gruszczyński
2007-08-03 0:27 ` [gentoo-dev] " Steve Long
2007-08-03 1:09 ` Steve Long
2007-08-03 9:25 ` Filip Gruszczyński [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=1be78d220708030225o6d70b717mbe6e26b4e8d7e46c@mail.gmail.com \
--to=gruszczy@gmail.com \
--cc=gentoo-dev@lists.gentoo.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