On Sunday 11 July 2010 08:41:46 James Rhodes wrote:
> n any case, it's a simple system which will probably suit your needs for
> installing applications when you install the distribution (other than just
>  a basic tarball since it's capable of resolving dependencies and
>  organising applications).
> 


Seems like a solution looking for a problem.

I cant myself see how  'package management'  fits with compile from sources 
philosophy.  Automated build procedures yes,  but package-management  meaning  
pre-compiled libraries, and executables  in   specified locations?      There 
are loads of other distributions that have a head start for this.  Why re-
invent the wheel?

I have also seen  build    schemes   for 'embedded-linux'  efforts   clustering 
  
around boards  such as    beagleBoard   and blackfin based boards    that often 
go out of their way to obfuscate.   There   scripts requiring  online  source-
fetches and  compile/install with passage of root passwords  (whilst on the  
www)  is the norm!!    This should have no place in the  philosophy of 
learning to build  from sources,  building securely and  tailoring to your 
needs.

 
And one wonders  what a basic tarball is?   I have been dabbling with 
lfs/clfs/blfs/cblfs for ~ 6 years now  and Linux for just 11 years.   I find 
that the numerous programs that go to make up a distribution have their own 
peculiarities -especially the more useful ones. For example I have compiled  
kde4  from version 4.1.0  to 4.4.5  and I still find it difficult.

-my 0.99penny coin's worth
luxInteg
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to