From: Bart Lauwers <blauwers@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] coveted features
Date: Mon, 29 Dec 2003 19:02:40 +0100 [thread overview]
Message-ID: <200312291902.40803.blauwers@gentoo.org> (raw)
In-Reply-To: <288B2E98-3891-11D8-BB5E-0003938E7E46@gentoo.org>
Pieter,
Imagine the expert system is 'screen' or interacts similarly to it, meaning
it can read all output from portage and it can send a command line back (i.e.
emulate a real user). This would basically put the system out of portage so
why make it a requirement? So that during development it can be accounted for
that some things will want unfiltered output and input. Maybe I'm not making
myself clear again so let me know if you still don't see what I mean now.
I would in no way expect portage to deliver the expert system but it should
IMHO provide the frame on which one could be built.
Bart
> > 8. have hooks for an expert system that can deal with compile errors
>
> This request is too abstract. This could become very interesting in
> combination with the freshmeat sync feature that was requested on -dev
> earlier. This is why I like looking at ebuild in a directory as a
> knowledge base (KB):
> there are learning techniques which can be used to , based on 'past'
> knowledge, provide about-data (dependency info, features, ...) for a
> newer version. The problem however is the howtodata (some patches might
> no longer apply, ...) it would be nice to have a reasoning system for
> that too, but I think this falls outside the scope of the current
> effort.
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-12-29 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312271631.45947.blauwers@gentoo.org>
2003-12-28 23:02 ` [gentoo-portage-dev] coveted features Daniel Robbins
2003-12-29 17:55 ` Bart Lauwers
2003-12-29 19:22 ` [gentoo-portage-dev] Re: [gentoo-doc] " Sven Vermeulen
2003-12-29 21:31 ` Jeremy Maitin-Shepard
2003-12-29 23:55 ` Bart Lauwers
2003-12-30 4:45 ` Jeremy Maitin-Shepard
2003-12-30 0:13 ` Bart Lauwers
2004-01-07 21:12 ` Jason Mobarak
[not found] ` <288B2E98-3891-11D8-BB5E-0003938E7E46@gentoo.org>
2003-12-29 18:02 ` Bart Lauwers [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=200312291902.40803.blauwers@gentoo.org \
--to=blauwers@gentoo.org \
--cc=gentoo-portage-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