Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
From: Niclas Hedhman <niclas@hedhman.org>
Organization: Private
To: "Avalon Developers List" <dev@avalon.apache.org>
Subject: Re: Question: Sequence of execution in Merlin
Date: Wed, 21 Apr 2004 11:30:04 +0800
User-Agent: KMail/1.5
References: <003701c42720$85338780$fe01a8c0@corp.4tel.no>
 <c6469b$i3n$1@sea.gmane.org> <004501c42726$79a2f620$fe01a8c0@corp.4tel.no>
In-Reply-To: <004501c42726$79a2f620$fe01a8c0@corp.4tel.no>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404211130.04294.niclas@hedhman.org>

On Wednesday 21 April 2004 06:26, Nader Aeinehchi wrote:
> To give some idea, please see the following excerpt from a configuration
> file.

The suggested changes as they stand, are IMO too far from the established 
path.

Boot-sequence IMHO, is a 'bad thing' as Merlin's mechanisms are overridden in 
damaging ways.

I am not sure what you are striving for and real-life use-cases would always 
help. Because this isn't new, but so far all presented use-cases are cases of 
incorrect underlying programming and asking for this feature for the wrong 
reasons.

Having additional information tied to the component is a different story, and 
we can discuss that later.


Niclas
-- 
+---------//-------------------+
|   http://www.bali.ac         |
|  http://niclas.hedhman.org   |
+------//----------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org