From: Gunter K. <gu...@pe...> - 2020-05-17 13:09:35
|
On 17.05.20 13:25, Me Self wrote: > Hello everyone > > Maybe a better solution would be to add a separate function, like > build_info()? If the need comes, the user can run os_info(), or any > name. This way people that don't want too much info disclosed can > choose when to add it, and those that don't mind can run that just > fine when running build_info(). > > Regards, > Vlad In the current git master of maxima build_info(); already contains much more information than it used to since many questions in the mailing list seemed to suggest that this was needed. My current build_info() is: (%i1) build_info(); (%o1) build_info(version= "branch_5_43_base_507_g546f8c3d6", timestamp="2020-05-16 23:13:45",host= "x86_64-pc-linux-gnu",lisp_name="SBCL", lisp_version="2.0.4.debian",maxima_userdir= "/home/gunter/.maxima",maxima_tempdir= "/tmp",maxima_objdir= "/home/gunter/src/maxima-code/binary/branch_5_43_base_507_g546f8c3d6/sbcl/2_0_4_debian" ,maxima_frontend="wxMaxima", maxima_frontend_version= "20.04.0-DevelopmentSnapshot_GTK3_OpenMP201511+Locks") Since the build_info() is a struct it should not be too compicated to extend it with more information, though, without risking to break pre-existing code. Kind regards, Gunter. |