gnewsense-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gNewSense-users] IMPORTANT: Formating error with the fmt.sh script


From: Luis Alberto Guzman
Subject: Re: [gNewSense-users] IMPORTANT: Formating error with the fmt.sh script & Problems with the kpvtab.py
Date: Sat, 15 Mar 2008 12:16:56 -0600

You see, even if we are starting this work, a lot of packages have been
done, and i tried to follow what i saw.

I highly recommend, that you and Marco talk about this issue.
You helping us with the script issue, and Marco for the experience that
he already got doing KFV. Together you could get some sweet conclusions
about how to handle the next adopted sections.

And i would like to settle the whole KVF "working mode" (way to proceed
in each possible case) in Documenting Your Work Kernel.

http://wiki.gnewsense.org/Main/DocumentingYourWorkKernel

So all the involved will know how to do it, and add some international
help, by translating it to another languages and teach all the user (who
wants to help) how to help in this huge effort.

I don't know any script language and i'm following the KFV work already
done.

What do you think? Maybe we could talk about this issue in the IRC
channel, for doing it more fluid. Or if not possible by the mailing
list.

Regards

El sáb, 15-03-2008 a las 22:50 +0800, Christophe Jarry escribió:
> Hi everybody,
> 
>  As I was checking the formating of tables containing the Kernel 
> drivers, I found out that the fmt.sh script didn't accept digits as 
> driver names. This means that all the 'ieee1394*' files in the 
> 'ieee1394' section would be written as 'ieee'. I've modified the script 
> to allow digits in the file/folder name.
> 
>  Moreover, as the urls naming problem pointed out by Bake Timmons is 
> important, I've modified the fmt.sh script to have urls as in 
> 'Ubuntu-hardy-linux-2-6-24-drivers-dma', the last part corresponding to 
> the relative path linux-2.6.24/drivers/dma whatever the absolute path.
> 
>  And, because I'm working on the stats script for the Kernel drivers, I 
> needed to have the number of all the files present in each folder, I've 
> then added this functionnality to the script.
> 
>  The resulting script's name has been changed in TableFormat.sh as I 
> think it's more intelligible for us.
> 
>  If you want to see results of this script, you can go to 
> http://wiki.gnewsense.org/Kernel/Image or to 
> http://wiki.gnewsense.org/Kernel/Ubuntu-hardy-drivers. The tables 
> created by the script are at the bottom of the pages each time (I've not 
> deleted previous tables, of course !).
> 
>  If our community agree, I suggest all of the Kernel Freedom Verifiers 
> using ONLY this script. This will make things easier if we want the 
> stats of the KPV as quick as possible. It will also require new created 
> webpages (new urls pointed by the script) to be completed with the work 
> already done and this is the most urgent task as the work is progressing.
> 
>  If everybody agree with that, I will update the 
> http://wiki.gnewsense.org/Main/DocumentingYourWorkKernel page and upload 
> the script (do someone know how to do that?).
> 
> 
>  I've also looked at the kpvtab.py and found that it assumes that: the 
> verification is already done (100%), all the drivers checked are free 
> (100%) and that all the folders contain only one file. This would 
> influence the stats script I'm writing and let us believe that a section 
> is completed while it is not. So, I strongly suggest all the Kernel 
> Freedom Verifiers using ONLY this script.
> 
> 
>  If someone find some bug, please inform the list as quick as possible, 
> I'll try to fix it as soon as possible,
> 
>  Thanks,
> 
>  Cheers,
> 
>   Pitof
> 
> _______________________________________________
> gNewSense-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gnewsense-users
-- 
Luis A. Guzmán García
http://www.gnewsense.org/Main:es/gNewSense
http://switnet.googlepages.com
gNewSense Usuario/Colaborador





reply via email to

[Prev in Thread] Current Thread [Next in Thread]