Public SourceMage Discussion List

[Seth Alan Woolley <seth AT positivism.org>]

If somebody wrote a specification for how we would store that info, they 
can put it into a bug report and give the developers something to shoot 
at after it has been discussed and agreed upon by those involved.  
Otherwise, nothing will get done.

I prefer before we start writing code to sit down and think about the 
process and document it.  This also gives documenters a better hope at 
understanding the implementation so as to better write it up for 
non-developers.

I figure we take the depends info and put that in a file of a known 
location.  Do the same with the configure file for persistent options 
and include a way of describing what architecture it is.  To be unixy, 
we could put a lot of the critical arch data in the filename itself so 
finding the correct one is easy.  Maybe we can include the last four 
digits of hash of the most important configure options in the filename.

At least we should have three or four people bouncing around the "best" 
way in a bugzilla bug.

Seth

On Mon, Oct 04, 2004 at 10:50:02PM +0200, Andrew ruskie Levstik wrote:
> I'm guessing we could expand this to also
> include the cache(though that would need some data in the cache files 
> themelfs)
> like optimizations and arch and config info.
> 
> This would be usefull for those ppl that acctualyl want binary only.

-- 
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id EF10E21A = 36AD 8A92 8499 8439 E6A8  3724 D437 AF5D EF10 E21A
http://smgl.positivism.org:11371/pks/lookup?op=get&search=0xEF10E21A
Security Team Leader Source Mage GNU/Linux http://www.sourcemage.org

Attachment: pgpMlnUpka3Ns.pgp
Description: PGP signature