It is opensource & free (3rd party) pkg-mngr (package manager) for macOS, etc, & it does not steal your usage/private data. If you use homebrew: use OPT OUT option/command, Notice / WARNING / CAUTION : homebrew is opensource pkg-mngr but this tool uses Google Analytics to collect usage telemetry.Homebrew was built 7yrs after MacPorts pkg-mngr (formerly known as DarwinPorts). It is opensource & free (3rd-party) pkg-mngr for macOS, etc. Pkg-manager tool internally includes option to use (some form of) authentication & verification for any download. Either download src/bin over secure/encrypted connection from original-author's website, OR, you must use OpenPGP/GPG/PGP based authentication to make sure downloaded src/bin is indeed actually released by actual original author. You must not download & compile & use source (src) or binary (bin) from any non-original author website or post. macOS has native pkg-mngr known as App Store, it has various or too many unfair restrictions & walls, set by macOS dev apple, does not allow various types of open-source apps, etc, So that is why sometime we need to use 3rd-party pkg-mngr. “Trust” is more important & safer & secure, than “Fast”/“Slow”. When binaries are properly compiled & built in your own OS/distro then that is more trustworthy & better, than faster & directly download (pre-built) binaries. Some (3rd-party) pkg-mngr downloads binary that is pre-built with already patched source for your OS/distro. Usually package's maintainer patches the original-source to make it suitable for compile/run in target OS/distro. Some (3rd-party) pkg-mngr by default downloads package's source (and dependencies / pre-requisites) & also auto compiles it in your OS/distro to create/build binary file(s). If previous steps are not possible for you, (because, “patching” requires software development, and OS/distro platform, and harwdare platform based knowledge, etc) then in such cases using 3rd-party package-manager (pkg-mngr) may be necessary for you. Compile (compilation) process builds package's binary (aka: executable), etc file(s). So your next best option is: compile the source obtained from original author/developer, after you patched the source to make it compatible & compilable for your OS/distro. If original author shares only source, then that means author wants you to compile source. (Package's source (src) code/file needs to be compiled to build package's binary/executable (bin) file⒮). So in such cases, next best option is: obtain the (src/bin) package from original author's website for your OS/distro via secure conneciton. But often OS/distro dev or computer MFR does not update their pre-included packages, or uses older version, or does not include option for user to obtain other/related packages (from OS/distro dev or computer MFR). Atleast fork the project to have a functional build without the ridiculous policies, or are we just waiting for Hexchat to make this completely obsolete?ĭon't believe me? Go to the Github page and see for yourself how many orders of magnitude better the Aqua version really is.Notice/CAUTION : Usually most of the time, using source (or binary) packages distributed from primary/original author/developer is much much better than next-level (aka: downstream) package distributors: like, OS/distro developer (dev), computer MFR (manufacturer), etc distributed packages, And usually most of the time OS/distro dev's or computer MFR's distributed package is better than 3rd-party Package-Manager (pkg-mngr) maintainer distributed package. The last usable, reliable, stable release is Aqua 0.17.3 from 3 years ago, without the disgusting restrictions the last time X-Chat could be called "software", not an "app". The app sandboxing reduces all plugin functionality to moot, what is the point of having Python/Perl plugins when 98% of the system remains inaccessible? Before this abomination took hold, X-Chat Aqua was decent software rather than fixing up the codebase and bringing it on par with Linux/Windows, we have this. Adding it to the appstore meant adhering to Microsoft's "guidelines", which effectively strip down fully functional computer software, into measly sub-par, semi-functional "apps". This was good software until the current dev became hellbent on distributing it through the appstore rather than traditional means.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |