Keyboard input / init + questions

[Jerome Martin]

I cannot copy/paste it right now, but I have interesting messages in a
screenshot attached.
Tell me what you think.

On Sun, Sep 26, 2010 at 10:48 PM, Jerome Martin <tramjoe.merin at gmail.com>wrote:

> Ray,
>
> Is the debug logged saved somewhere ? Because with my setup copying it from
> the console is going to be tedious...
>
> ++
>
>
> On Sun, Sep 26, 2010 at 10:36 PM, Jerome Martin <tramjoe.merin at gmail.com>wrote:
>
>>
>>
>> On Sun, Sep 26, 2010 at 10:29 PM, Ray Strode <halfline at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> On Sun, Sep 26, 2010 at 3:40 PM, Jerome Martin <tramjoe.merin at gmail.com>
>>> wrote:
>>>
>>> > 1) I upgraded to git version, still no luck with the keyboard messup
>>> with
>>> > init (from sysvinit debian squeeze) when it starts the rc2.d after rcS
>>> > execution.
>>> Can you post a log booted with plymouth:debug ?
>>>
>>
>> Mmmh, I'll try to get that setup back online and do that ASAP.
>>
>>
>>>
>>> [..snip..]
>>> > And the patches themselves in attached file...
>>> Most of these changes are script specific, so I'll leave this stuff
>>> for Charlie to respond to.
>>>
>>
>> OK.
>>
>>
>>>
>>> > the current git version certainly deserves a
>>> > proper release and some documentation though ...
>>> Right, I was going to do some logging changes before doing a 0.8.4
>>> release, but maybe i'll do those changes after the release.
>>>
>>> Documentation is something very much lacking in plymouth.  I want to
>>> rectify that before 1.0.
>>>
>>
>> <nod>
>>
>>
>>>
>>> > 5) As a sidenote, I did a quick debian packaging of the git version,
>>> but had
>>> > to adapt a bit the debian package rules from squeeze because it assumed
>>> that
>>> > plymouth original sources already had autoconf ran there, when those
>>> that I
>>> > downloaded had an autogen.sh script ... This is weird, and it is either
>>> an
>>> > unclean package in debian OR the fact that you released last time with
>>> > autogen.sh already ran. Is that the case ?
>>> the autogoo model is a little weird here.  The version of the source
>>> in the tarball contains generated files that aren't checked into
>>> version control.  When making a release, I do
>>>
>>> "make distcheck"
>>>
>>> which creates the tarball and adds the generated files to the tarball.
>>>  If you're just building a snapshot you can do:
>>>
>>> "make dist"
>>>
>>> which does the same thing but skips a bunch of checks and a test
>>> compile that take a lot of time.
>>>
>>
>> Mmmhh. But against which makefile ? You need to generate it first don't
>> you ?
>> So the release from git tree would be ./autogen.sh; ./configure OPTIONS
>> and then your make distcheck ?
>>
>> Best,
>> --
>> Jérôme Martin
>>
>
>
>
> --
> Jérôme Martin
>



-- 
Jérôme Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/plymouth/attachments/20100926/33574455/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clnode1 @ 2010-09-26 23:09:26.png
Type: image/png
Size: 12731 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/plymouth/attachments/20100926/33574455/attachment-0001.png>