OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => OpenBSD => Topic started by: ZDevil on June 07, 2007, 02:47:39 pm
-
Don't want to go far off-topic from the "Package Repository" thread, so let me start a new one here concentrating on managing the ports collection on Zaurus.
Two questions to start with:
Q1. What would be the easiest AND safest way to clean up the sources fetched and the files created during make?
I see people talking about "cd /usr/ports && make distclean".
Does it work for Z? I just want to be cautious not to mess up the port tree.
Q2. What would be the best way to keep the ports collection most up to date?
I learn cvsup from http://www.openbsd101.com/updating.html#u6 (http://www.openbsd101.com/updating.html#u6), however when i tried to set it up, there was an error saying cvsup is for i386 machines only.
It seems another way is to overwrite /usr/ports with the latest ports.tar.gz from pub/OpenBSD/snapshots/, but it takes so quite a long while to uncompress the tarball. The nice thing about cvsup is that it only update the ports when application while leaving the unchanged ports intact, so it's fast and more convenient. Any hope or method to get cvsup running on Zaurus?
-
Q1. What would be the easiest AND safest way to clean up the sources fetched and the files created during make?
I see people talking about "cd /usr/ports && make distclean".
Does it work for Z? I just want to be cautious not to mess up the port tree.
i think there's no problem in doing the make dist=clean
i've already done it and you'll gain many bytes !
-
Q2. What would be the best way to keep the ports collection most up to date?
I learn cvsup from http://www.openbsd101.com/updating.html#u6 (http://www.openbsd101.com/updating.html#u6), however when i tried to set it up, there was an error saying cvsup is for i386 machines only.
It seems another way is to overwrite /usr/ports with the latest ports.tar.gz from pub/OpenBSD/snapshots/, but it takes so quite a long while to uncompress the tarball. The nice thing about cvsup is that it only update the ports when application while leaving the unchanged ports intact, so it's fast and more convenient. Any hope or method to get cvsup running on Zaurus?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=162803\")
look here :
[a href=\"https://www.oesf.org/forums/index.php?showtopic=20790]https://www.oesf.org/forums/index.php?showtopic=20790[/url]
i think you'll find answers to many of your questions
by the way i've compiled mplayer yesterday (night!) , i'll give it a try later
-
Thanks! I should follow the posts here first. It seems sometimes what is said in the official documentation is not totally applicable to Z.
-
Thanks! I should follow the posts here first. It seems sometimes what is said in the official documentation is not totally applicable to Z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=162824\"][{POST_SNAPBACK}][/a][/div]
apparently what is working is
make clean
-
there's something i don't understand with ports building :
assuming you've untared ports.tar.gz in /usr, why is openbsd always fetching some sources on the network ? should all necessary sources yet be in /usr/ports ???
another question:
if i've no network on the zaurus, can i download some source files on my destkop, put it on a cf card and have the make process find this xxx.tar.bz2 file ??? if yes, how can i do this ?
-
No, the ports.tar.gz (just a tarball of 10MB+) does not contain the sources tarballs itself. It only contains the portlist and the makefiles.
I think you can put the source files on a card, and then do a symlink from the correct location on the port tree, e.g. devel/chmlib. A glance at the existing source files should tell where to put them.
Or perhaps simply do a symlink of the whole port tree to a path of a memory card will do?
But then one tradeoff is dependency tracking and patching may not work, because all the dependent program sources and patches are downloaded automatically at the beginning of the build process.
-
No, the ports.tar.gz (just a tarball of 10MB+) does not contain the sources tarballs itself. It only contains the portlist and the makefiles.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163112\"][{POST_SNAPBACK}][/a][/div]
ok i understand better !
well, so is it possible to download ALL needed files at the start ot the compilation process THEN compile all sources ???
-
No, the ports.tar.gz (just a tarball of 10MB+) does not contain the sources tarballs itself. It only contains the portlist and the makefiles.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163112\"][{POST_SNAPBACK}][/a][/div]
ok i understand better !
well, so is it possible to download ALL needed files at the start ot the compilation process THEN compile all sources ???
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163121\"][{POST_SNAPBACK}][/a][/div]
I think it's make fetch but I'm not 100% sure.