public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: dams <dams@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Cc: gentoo-perl@gentoo.org
Subject: Re: [gentoo-perl] PortageXS / Gentoo::Portage
Date: Fri, 6 Oct 2006 10:41:25 +0100	[thread overview]
Message-ID: <20061006104125.7b46d57f@localhost.localdomain> (raw)
In-Reply-To: <200609180101.19772.ian@gentoo.org>

On Mon, 18 Sep 2006 01:01:19 +0200
Christian Hartmann <ian@gentoo.org> wrote:

> Hi all,
> 
> I promised that I'll keep you posted about the progress I'm making.
> First of all Gentoo::Portage it's now called PortageXS just because
> of some reasons:
> 
> - there already sits a Gentoo::Portage on my harddrive thanks to
> g-cpan ;)
> - if you don't like it I'll continue working on PortageXS anyways for
> my own toys - different namespace - no harm done :)
> - I like the name 'PortageXS' because it pretty much describes what
> it does: access portage stuff using perl; providing an abstraction
> layer to portage
> - it's based on up2date-ng and @otherscripts - not based on
> Gentoo::Portage
> 
> Grab the ebuild here:
> http://download.iansview.com/gentoo/tools/PortageXS/PortageXS-0.01_pre1.ebuild

As I told to Christian, I currently have no internet access at home,
but as soon as I have, I'll check this out. Thanks for coding stuff :)

cheers,
dams
-- 
gentoo-perl@gentoo.org mailing list



WARNING: multiple messages have this Message-ID (diff)
From: dams <dams@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Cc: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] PortageXS / Gentoo::Portage
Date: Fri, 6 Oct 2006 10:41:25 +0100	[thread overview]
Message-ID: <20061006104125.7b46d57f@localhost.localdomain> (raw)
Message-ID: <20061006094125.EKy4rTA3nKAlnzXTFQoopL5ydvy55vKiZeY7i4gg9FY@z> (raw)
In-Reply-To: <200609180101.19772.ian@gentoo.org>

On Mon, 18 Sep 2006 01:01:19 +0200
Christian Hartmann <ian@gentoo.org> wrote:

> Hi all,
> 
> I promised that I'll keep you posted about the progress I'm making.
> First of all Gentoo::Portage it's now called PortageXS just because
> of some reasons:
> 
> - there already sits a Gentoo::Portage on my harddrive thanks to
> g-cpan ;)
> - if you don't like it I'll continue working on PortageXS anyways for
> my own toys - different namespace - no harm done :)
> - I like the name 'PortageXS' because it pretty much describes what
> it does: access portage stuff using perl; providing an abstraction
> layer to portage
> - it's based on up2date-ng and @otherscripts - not based on
> Gentoo::Portage
> 
> Grab the ebuild here:
> http://download.iansview.com/gentoo/tools/PortageXS/PortageXS-0.01_pre1.ebuild

As I told to Christian, I currently have no internet access at home,
but as soon as I have, I'll check this out. Thanks for coding stuff :)

cheers,
dams
-- 
gentoo-perl@gentoo.org mailing list



  reply	other threads:[~2006-10-06  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 23:01 [gentoo-perl] PortageXS / Gentoo::Portage Christian Hartmann
2006-10-06  9:41 ` dams [this message]
2006-10-06  9:41   ` dams

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=20061006104125.7b46d57f@localhost.localdomain \
    --to=dams@gentoo.org \
    --cc=gentoo-perl@gentoo.org \
    --cc=gentoo-perl@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