[SOLVED] Meaning of -noarch- in the name of some slack packages.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi:
bittorrent-4.4.0-noarch-2.tgz is certainly a binary one, as having installed it with installpkg proves. What I must understand, according to Sayan, is that the binaries contained in this package will run on more than one architecture? This is impossible!
No, it is not. The bittorrent program is written in Python. Python is an interpreted language and runs on any computer that has the Python interpreter installed, regardless of its architecture. It is not a binary.
No, it is not. The bittorrent program is written in Python. Python is an interpreted language and runs on any computer that has the Python interpreter installed, regardless of its architecture. It is not a binary.
I see. As in the old days of the basic interpreter, run by either the O.S. or firmware. It must be the astonishing speed of current CPU's what favored the return of interpreted languages. Regards.
It must be the astonishing speed of current CPU's what favored the return of interpreted languages.
That, and a different approach than in the old days. In the old days the code of interpreted languages was directly interpreted. In Python, for example, the code will be compiled to a byte-code on runtime, and this byte-code will run in a virtual machine. If you run a Python application you will find files with the .pyc ending. These are the compiled instructions.
I don't know if interpreted is really the right word in this context.
@TobiSGD: So Sayan was right after all. There _is_ compilation. And I now see the necessity to speak of byte-code as opposed to the intermediate compilation generated code. This is all very instructive. Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.