On Thursday 20 of February 2020 23:05:27 Dr. Nikolaus Klepp wrote: > Hi Slavek, > > Anno domini 2020 Thu, 20 Feb 21:34:16 +0100 > > Dr. Nikolaus Klepp scripsit: > > Anno domini 2020 Thu, 20 Feb 20:37:30 +0100 > > > > Slávek Banko scripsit: > > > On Thursday 20 of February 2020 20:00:41 Dr. Nikolaus Klepp wrote: > > > > Hi Slavek, > > > > > > > > Anno domini 2020 Thu, 20 Feb 19:22:13 +0100 > > > > > > > > Slávek Banko scripsit: > > > > > Hi Nik, > > > > > > > > > > On Thursday 20 of February 2020 17:27:21 Dr. Nikolaus Klepp > > > > > wrote: > > > > > > > > > > > > > > > It is very interesting that the manual pages are not compressed > > > > > on your system. I am not aware that I did something special on > > > > > my test machine (except freebsd-update, pkg update and portsnap > > > > > update) and the pages are now compressed automatically. That's > > > > > why I edited all pkg-lists to install compressed man pages. > > > > > > > > > > BTW, my test machine: FreeBSD 12.1-RELEASE-p2 > > > > > > > > I did the same, pkg upgrade & freebsd-update. But what I forgot to > > > > mention: Yesterday I tested the build with just updating git, and > > > > I think I forgot the "make clean". That test did not hit the > > > > manpage-not-compressed-problem. Today I deleted the whole > > > > tde-packaging-directory, then pulled from git, and was faced with > > > > the not compressed manpages. Same goes for the other errors. > > > > > > You do too "portsnap fetch && portsnap update"? Maybe it may be why > > > our systems differ. In fact, I still don't know if I should use > > > subversion instead of portsnap. The tutorials usually recommend > > > portsnap, so I also use portsnap. > > > > Well, yes, but "portsnap fetch && portsnap update" does not rebuild > > any of the packages that were built from ports when I compiled TDE > > some weeks ago. So there are definity differences. Maybe all > > build-necessary packages should be installed from packages, not ports? > > I have to correct myself: "portsnap fetch && portsnap update" does make > all the difference. I just redid all the steps, this time with updated > ports. Turns out, all packages that were built from ports are updated in > the process of rebuilding TDE :) > > So all the errors are gone (tde-i18n-de does not count)! You did a great > job! (And I need to update my docs :) ) > > Nik > > > Nik > > > > > Cheers On my testing machine, I have most of the dependencies installed from binary packages. I always try to avoid compilations other than the Trinity ports. I intend to prepare a readme with basic instructions. There I want to mention the packages that should be installed before building Trinity ports. However, it needs some time... Cheers -- Slávek --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
