Unwanted Optimizations

Neven Has haski at sezampro.yu
Wed Apr 3 04:34:06 PST 2002


On Tue, Apr 02, 2002 at 07:26:21PM +0300, Silviu Julean wrote:
> > You could use a <stage> element do simply replace a <prebuild> element
> > if you wanted to. But it could do more as well.
> 
> Are you going to REPLACE the current DTD with <stage>-like tagging or going
> to use it in addition, to specify more stage information *if wanted*?

No, the idea is to replace all <*build> elements, <chroot>,
<setenv>, and <su> (which didn't last long anyway) with <stage>.

> <chroot dir="&LFS;">
> 	<prebuild>
> 	... Do some stuff
> 	</prebuild>
> </chroot>
> 
> i'd choose the last one... Why get complicated when the current synthax is
> doing the job? And to specify more information,

Actually, the last one is more like:

<chroot dir="&LFS;">
	<su user="lfs">
		<prebuild>
		... Do some stuff
		</prebuild>
	</su>
</chroot>

Plus, you have to set the base directory for every element inside,
because there is no way now to do that globally. More precisely, there
isn't a good _place_ to do that. Unless it's only <package>-wide, where
we could use it in <packageinfo>.

The thing is - if you're using a lot of different elements, there are
too many nesting in the current syntax and the proposed <stage> makes
it clearer. But if you're not using that many, the current syntax is
clearer and <stage> is more or less "not needed", so to speak. :/
Well, IMO at least.

> <prebuild info="Fooing" comment="This performs a foo-ing (using foo-3.2.5 in
> /usr/bin/foo) before the actual compilation">
> 
> just like the alt="" parameter used in HTML <img> would do.
> 
> IMHO your DTD specifies way too many stand-alone tags, when more parameters
> could be used.

I think we already have an agreement to use the name of the stage as
a parameter, not in its own tag. That makes a syntax clearer. At least
when few elements are used, since that's when the <stage> is most
"vulnerable".

> Neven: i'm not here to complain, i know it's been a damn hard (team)work;
> all i'm saying is that, thinking of all end-[l]users, this great automation
> system could be used by non-LFS users too.

Well, that's the idea. :)

BTW, you don't have to persuade me, I'm not the one who decides what
will go in the syntax, what won't, and stuff like that.

I guess you'll have to persuade Jesse how much this sucks. ;)

(Just kidding of course, I think it's a good idea, we'll just have to
make the syntax the best we can.)

> PS: if you're not replacing any tags in the current DTD, just ignore this
> (tho my remark goes a bit deeper than that)

No, as I said above, the whole idea of <stage> is to remove all other
"specific" elements and make <stage> a generic one.


Neven

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe alfs-discuss' in the subject header of the message



More information about the alfs-discuss mailing list