Hi There! I want to migrate a selfmade proprietary LFS embedded powerpc system to follow the CRUX look&feel by hosting port repositories for my architecture and use the crux package tools to keep several of those machines in sync and up to date. 1. Is there some documentation available for the lazy guys (i.e. from the CRUX-PPC folks) to avoid duplicate brainwork? Any pointers would be appreciated. 2. Is it possible / a good idea to build the ports db by package-by-package migration (installation / update) via my own ports tree just starting it, installing over the existing system? And once this is finished, is it a good idea to remove the files carefully from the filesystem which are not part of a package in the db? Is there a way to show/remove stale files from the system which are not needed (not in the db) anymore? Thanks, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm.de Phone: +49-89-741518-50 Fax: +49-89-741518-19
Clemens Koller wrote:
Hi There!
hello
I want to migrate a selfmade proprietary LFS embedded powerpc system to follow the CRUX look&feel by hosting port repositories for my architecture and use the crux package tools to keep several of those machines in sync and up to date.
Well i guess you should just install ports and pkgutils over it and start using it...
1. Is there some documentation available for the lazy guys (i.e. from the CRUX-PPC folks) to avoid duplicate brainwork?
yep we've been lazy lately but there is a crux-ppc 2.2 (it's alpha but it's quite usable) available if you go to seek on our "improvements" forum...
2. Is it possible / a good idea to build the ports db by package-by-package migration (installation / update) via my own ports tree just starting it, installing over the existing system?
the plain crux (or crux-ppc, if you go back a couple of versions of it you might find a more readable one) Makefile should be ok to do that. anyway installing them in another path and then chrooting in there (the way the makefile does with make bootstrap) should be better...
And once this is finished, is it a good idea to remove the files carefully from the filesystem which are not part of a package in the db?
installing everything somewhere else and using the new environment should be a better idea... bye giorgio P.S.: sorry for sending to the mailing list from the wrong address... -- NullPointer || GnuPG/PGP Key-Id: 0x343B22E6 http://cruxppc.sunsite.dk
Hi, Giorgio!
1. Is there some documentation available for the lazy guys (i.e. from the CRUX-PPC folks) to avoid duplicate brainwork?
yep we've been lazy lately but there is a crux-ppc 2.2 (it's alpha but it's quite usable) available if you go to seek on our "improvements" forum...
Okay, is there a separate mailing list where the crux-ppc people get together? I don't speak italian, so crux-it might not be very helpful to me. (BTW: cruxppc.sunsite.dk is way too slow for serious work over here) I think that my system - an MPC8540 embedded PPC (BookE, e500 core) should be able to get along with the default ppc stuff most of the time.
2. Is it possible / a good idea to build the ports db by package-by-package migration (installation / update) via my own ports tree just starting it, installing over the existing system?
the plain crux (or crux-ppc, if you go back a couple of versions of it you might find a more readable one) Makefile should be ok to do that.
Jup, I've just built pkgutils + friends. Is there an outline of an diff of the ppc vs. the x86 crux infrastructure somewhere documented?
installing everything somewhere else and using the new environment should be a better idea...
Yep, good point. Maybe I try some overlay filesystem stuff and separate the old from the new stuff that way. I don't like the dual-root approach somehow yet... hmm... Best greets, Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm.de Phone: +49-89-741518-50 Fax: +49-89-741518-19
Hi, On Wed, Sep 06, 2006 at 11:51:19 +0200, Clemens Koller wrote:
Hi There!
I want to migrate a selfmade proprietary LFS embedded powerpc system to follow the CRUX look&feel by hosting port repositories for my architecture and use the crux package tools to keep several of those machines in sync and up to date. [...] 2. Is it possible / a good idea to build the ports db by package-by-package migration (installation / update) via my own ports tree just starting it, installing over the existing system?
Hi, here's the approach I chose for the sparc port: http://jw.tks6.net/files/crux/sparc-porting.txt The primary benefit of this approach is that you don't pollute the working (non-crux) system while getting a _clean_ crux chroot you can base further work on. HTH, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
participants (3)
-
Clemens Koller -
Giorgio Agrelli -
Johannes Winkelmann