From: Bill Anderson <bill@noreboots.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild, ip6tables headaches, kernel confusion, xinetd vs. tcpwrappers
Date: Wed, 10 Jan 2001 10:40:42 -0700 [thread overview]
Message-ID: <3A5C9E9A.7090907@noreboots.com> (raw)
In-Reply-To: 20010110081201.D7562@cvs.gentoo.org
drobbins@gentoo.org wrote:
> On Wed, Jan 10, 2001 at 11:06:54AM +0100, Achim Gottinger wrote:
>
>
>> autofs-4.0.0_pre9.ebuild should work. Maybe Daniel can document the naming
>> pattern somewhere on the net.
>
>
> There's some (old but mostly correct) documentation at the beginning of
> /usr/lib/python/portage.py that covers how the version numbers work.
Oooh, so Portage has python libraries to work with it, or is it done
using python?
next prev parent reply other threads:[~2001-01-10 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010108190102.65304328A2@cvs.gentoo.org>
2001-01-10 7:55 ` [gentoo-dev] ebuild, ip6tables headaches, kernel confusion, xinetd vs. tcpwrappers Justin Vander Ziel
2001-01-10 8:13 ` Jerry A!
2001-01-10 8:27 ` Thomas Flavel
2001-01-10 9:21 ` [gentoo-dev] ebuild, ip6tables headaches, kernel confusion,xinetd " Achim Gottinger
2001-01-10 10:55 ` [gentoo-dev] mission critical changes 8) (was: ebuild, ip6tables headaches, kernel confusion, xinetd vs. tcpwrappers) Morgan Christiansson
2001-01-10 11:17 ` Thomas Flavel
2001-01-10 11:57 ` Morgan Christiansson
2001-01-10 17:23 ` [gentoo-dev] no more long subject lines! :) drobbins
2001-01-10 17:06 ` [gentoo-dev] boot pretty drobbins
2001-01-10 20:47 ` Morgan Christiansson
2001-01-10 23:16 ` [gentoo-dev] Installation frontend Thomas Flavel
2001-01-10 23:29 ` drobbins
2001-01-10 14:56 ` [gentoo-dev] ebuild, ip6tables headaches, kernel confusion, xinetd vs. tcpwrappers drobbins
2001-01-10 8:57 ` Bill Anderson
2001-01-10 9:17 ` Jerry A!
2001-01-10 15:06 ` drobbins
2001-01-10 10:06 ` Achim Gottinger
2001-01-10 15:12 ` drobbins
2001-01-10 17:40 ` Bill Anderson [this message]
2001-01-10 17:57 ` drobbins
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=3A5C9E9A.7090907@noreboots.com \
--to=bill@noreboots.com \
--cc=gentoo-dev@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