On 12/24/2013 07:39 PM, John Burrell wrote:
>> Hello there,
>>
>> After many months since lfs systemd branch was created, I am pleased to
>> announce that I consider it being usable for everyone that wants to use it.
>>
>> I've managed to add missing bits to the branch today and doing that I've
>> finished what it was necessarry to bring it up to par with current lfs
>> development. There are some minor things missing like dependencies for
>> new packages, but I do not consider it critical to affect anything
>> related to the system built using the mentioned instructions.
>>
>> In another thread, Bruce mentioned that:
>>
>> "We plan on the next LFS version on March 1st with a package freeze
>> probably around mid-February."
>>
>> We will try to follow LFS freeze and release date and if it seems
>> possible, we will release lfs-systemd-stable <whatever the next stable
>> version is> along with lfs-stable.
>>
>> For anyone out there who has spare time and motivation, I'd like to test
>> the instructions and report back if there are any problems. I will also
>> accept any fixes that may concern lfs systemd, be it a spelling or
>> gramatical fix, instructions fix or even instructions enhancements.
>>
>> You can clone lfs-systemd book using svn co
>> svn://svn.linuxfromscratch.org/LFS/branches/systemd
> 
> A small request re. the svn cloning - 
> 
> When the book is downloaded using svn, it creates systemd/BOOK
> which contains all the files except one dir.
> 
> The directory .svn doesn't sit under BOOK, it's under systemd.
> 
> Would you change it please so that .svn is under BOOK which would then be the 
> same as all the other versions when they are svn'd.
> 
> Thanks and happy holidays
> 
> jb.                                     
> 

Just add /BOOK to the end of svn co url.

svn co svn://svn.linuxfromscratch.org/LFS/branches/systemd/BOOK systemd

Done!



-- 
Note: My last name is not Krejzi.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to