public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: archfs - filesystem for rdiff-backup archives
Date: Fri, 03 Aug 2007 01:27:04 +0100	[thread overview]
Message-ID: <f8tsoc$gb0$1@sea.gmane.org> (raw)
In-Reply-To: 1be78d220708021247i6d32327bifc31e7de62917d6a@mail.gmail.com

emerge: there are no ebuilds to satisfy "archfs".

Perhaps a link to the homepage/ overlay might be handy? ;)

This is not "something that's about the technical development of our tree"
so it might be considered off-topic (interesting though it might be.) As a
general rule, the Unsupported Software forum is a good place to get
feedback from users til something is releasable. (Apologies if you've
already gone thru that process, just mention it and give the url in that
case.) At that point getting feedback from devs as to it's suitability for
inclusion is acceptable, aiui, although even then you're probably just
going to get told to get on #gentoo-sunrise (irc.freenode.org) and work on
getting it into the main overlay before it makes the portage tree. (Unless
ofc a dev wants to pick it up out of interest.)

BTW I don't recommend autotools (there's a reason they're called autohell ;)
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.)


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-08-03  0:30 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   ` Steve Long [this message]
2007-08-03  1:09     ` [gentoo-dev] " Steve Long
2007-08-03  9:25     ` Filip Gruszczyński

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='f8tsoc$gb0$1@sea.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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