Hello.

This is follow up about sddm+lxqt contribution
and comment about the blfs-basic thread reading suggested
by Ken.

1) Seems I proposed myself to take care of page
    about lxqt and sddm (chapter 26).

    The best way for me to handle it, is to have
    access to commit within a specific git branch
    where modifications would be merged by editor.
    There is (of course) a gentlemen agreement
    to modify only pages under "contributor watch".

    Git tree should include a Makefile of some kind to allow
    a locale deployment (xml->html) allowing contributor
    to check locally modifications rendering (as it
    should appear on LFS web site).
    When satisfied contributor push Branch and
    editor will merge (or not) contribution at its
    own leisure.

2)  Noticed question about security patch burden, it
    is my say "this is a false problem".
    LFS and BLFS are learning tools, they are not
    intended to build a production system.
    so once (lets say) 8.2 was release (in book edition
    term), that's it, that's all.
    LFS|BLFS message is,
    "follow and understand book directives and you
     will have a working system Linux system, with the
     experience acquired you should be able track
     security issue or simple upgrade release for
     components which matter to you".

     The purpose of next release (lets say 8.3)
     is to make sure all selected most recent components are
     indeed working together with reproducible
     results. LFS/BLFS release are picture of a working
     Linux at a given time.

3)   About the SBU "estimated build time" I do not
     believe this is a contributor responsibility
     (hardware and compilation context are too
      variable).
     I think the best way is to have SBU collected from
     an all out generic verification build and injected
     directly within the proper XML page/chapter.


:-}
where I need to go to clone...

--

A bientôt
===========================================================
Jean-Marc Pigeon                        E-Mail: j...@safe.ca
SAFE Inc.                             Phone: (514) 493-4280
   Clement, 'a kiss solution' to get rid of SPAM (at last)
      Clement' Home base <"http://www.clement.safe.ca";>
===========================================================


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to