Hi again, Also I just notices intrigeri asked you a late question about your last week report on the tails-dev mailing list without any answer. Please see his last mail to you and tails-dev from August 04 about using a shell script. Did you answer to this question privately?
bert. On Fri, Aug 05, 2011 at 05:25:22PM +0200, berta...@ptitcanardnoir.org wrote: > Hi, > > I'm trying to catch up on this GSOC work, so I might be lacking some > informations to correctly understand everything. Don't hesitate to correct > me if I make any mistake. > > I've tested your previous 0.0.5 release as well as this week's one in a > fresh VM, and read your previous exchanges with intrigeri. > > On Fri, Aug 05, 2011 at 02:15:52AM +0800, † wrote: > > Hello. > > Current progress: > > > > obtain list of kb layouts and variants available (via python-xklavier) > > - DONE. > > populate layout widget with kb variants - DONE. > > merge feature/better_root_access_control branch - DONE. > > Confirm the above three DONE items. Well done! > > > apply correct layout after it's been chosen (both to present and > > following > > greeter widgets and to actual session) - postponed. > > verify that layout switching works after login - postponed > > version tag and update - DONE. > > As I understood, you were also supposed to upload a Debian package to your > tails repo, which I can't find. > > > > > Problems: > > > > tails-greeter is run under gdm's account but altering gdm PostLogon > > files (to set > > env variables) or locale compilation via localedef require root privileges. > > Seems like intrigeri already proposed a workaround to this last week, > please read again his answer to your report last week. > > > xklavier set and check layout without errors but it doesn't affect > > greeter nor > > following session. > > better_root_access_control feature requires env. variable to be set > > which is not > > possible yet. > > > Near-future plans: > > > > wait for answer from gdm and xklavier devs to figure out workarounds > > for current > > problems > > Do you have pointers to this conversation? I might be interested to follow > it, and eventually help you with it. > > > replace 2 widgets with 1 panel with same functionality > > test the result with tails > > Sounds to me that the next step to this dev would be to implement a way to > pass env variables too. > > > Additional notes: > > > > right now there are 2 "screens" which user moves through by pressing > > "next" > > button. That's rather ugly and is planned to be replaced with one of the > > following: > > > > 1) single "screen" with requests for both at the same time > > > > 2) 2 "screens" with language and layout requests on first one and admin > > password > > request on second one > > > > Which do you think is better and why? > > Please feel free to discuss it on irc this Saturday during regular > > meeting time > > or whenever you'll see max-gsoc > > I think intrigeri already made that clear when you started with 2 screens > that at the end we wanted to have only one screen with all options on it. > We don't want to bother too much our users with multiple screens. > > Another question: reading your commits, you removed the babel module > importation. Do you plan to put it back, or are you just getting rid of > it? In the latter case, you should also consider removing it from the > install dependencies of the Debian package in debian/control. > > See you tomorrow morning. > > bert. > > > _______________________________________________ > tails-dev mailing list > tails-dev@boum.org > https://boum.org/mailman/listinfo/tails-dev _______________________________________________ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev
