You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2id="table-of-contents">Table of contents <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
35
+
<h2id="table-of-contents">Table of Contents <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
36
+
<!-- vim-markdown-toc Marked -->
36
37
<ul>
37
-
<li><ahref="#table-of-contents">Table of contents</a></li>
38
38
<li><ahref="#requirements">Requirements</a></li>
39
39
<li><ahref="#installation">Installation</a></li>
40
40
<li><ahref="#command-line-options">Command line options</a></li>
<h2id="requirements">Requirements <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
<p><strong>PyRadio</strong> will periodically (once every 10 days) check whether a new version has been released.</p>
545
544
<p>If so, a notification message will be displayed, informing the user about it.</p>
546
545
<h2id="cleaning-up">Cleaning up <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
547
-
<p>Since version 0.8.7.3 (0.8.8-beta2), it is not necessary to follow the previous procedure any more; <strong>PyRadio</strong> will search and remove any previously installed files when the “<strong>-u</strong>” (uninstall) parameter is used.</p>
548
-
<p>This procedure will remove any <strong>Pyradio</strong> files installed in your system, but will leave instact <strong>PyRadio</strong> configuration files.</p>
549
-
<p>Windows users notice: This procedure <strong>will not</strong> uninstall python, mplayer, or git from your system.</p>
<p>In this example, running <em>devel/build_install_pyradio -u</em> has removed <strong>PyRadio</strong> python 3.8 system wide installation files, <strong>PyRadio</strong> python 2.7 system wide installation files, and <strong>PyRadio</strong> python 3.8 user installation files, found in the system.</p>
561
-
<p>I would recommend to execute <em>devel/build_install_pyradio -u</em> from time to time, and reinstall <strong>Pyradio</strong> right after its completion.</p>
562
-
<h3id="previous-cleaning-up-procedure">Previous cleaning up procedure</h3>
563
-
<p>As <strong>PyRadio</strong> versions accumulate, when building from source, one may have to <em>clean up</em> old installation files.</p>
564
-
<p>To do that, one has to observe the installation process in order to find out where the package is installed. The installation would complete printing the following messages (on <em>python 3.7</em>):</p>
Finished processing dependencies for pyradio==0.7.8</pre>
568
-
<p>From this we get that the installation directory is <strong>/usr/lib/python3.7/site-packages</strong>. This may be different though, depending on the distribution and python version used.</p>
569
-
<p>Let’s see what <strong>PyRadio</strong> files exist there:</p>
570
-
<pre>$ ls -d /usr/lib/python3.7/site-packages/pyradio*
<p>As we see, previous versions still exist in this system: <strong>0.7.6.2</strong> and <strong>0.7.7</strong>. These files (actually directories) can safely be removed:</p>
<p><strong>PyRadio</strong> will uninstall all previously installed versions when updated (using the <strong>-U</strong> command line parameter), so no extra steps are needed any more to house keep your system.</p>
578
547
<h2id="debug-mode">Debug mode <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
579
548
<p>Adding the “<strong>-d</strong>” option to the command line will instruct <strong>PyRadio</strong> to enter <em>Debug mode</em>, which means that it will print debug messages to a file. This file will always reside in the user’s home directory and will be named <em>pyradio.log</em>.</p>
580
549
<p>In case of a bug or a glitch, please include this file to the issue you will <atarget="_blank" href="https://github.com/coderholic/pyradio/issues">open at github</a>.</p>
<p>Finally, include the file produced in your report.</p>
590
559
<h2id="packaging-pyradio">Packaging Pyradio <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
591
560
<p>If you are a packager and would like to produce a package for your distribution please do follow this mini guide.</p>
592
-
<p><strong>PyRadio</strong> is able to update and uninstall itself, when installed from sources.</p>
593
-
<p>This is something you do not want to be available when your package is used; <strong>PyRadio</strong> should be updated and uninstalled using the distro package manager.</p>
594
-
<p>In order to accomplice that, you just have to change the <strong>distro</strong> configuration parameter in the <strong>config</strong> file.</p>
595
-
<p><strong>PyRadio</strong> will read this parameter and will disable updating and uninstalling, when set to anything other than “<strong>None</strong>”.</p>
596
-
<p>So, here’s how you do that:</p>
561
+
<p><strong>PyRadio</strong> is able to update and uninstall itself, when installed from source. This is something you do not want to be happening when your package is used; <strong>PyRadio</strong> should be updated and uninstalled using the distro package manager.</p>
562
+
<p>In order to accomplice that, you just have to change the <strong>distro</strong> configuration parameter in the <strong>config</strong> file. <strong>PyRadio</strong> will read this parameter and will disable updating and uninstalling, when set to anything other than “<strong>None</strong>”. So, here’s how you do that:</p>
597
563
<p>Once you are in the sources top level directory (typically “<em>pyradio</em>”), you execute the command:</p>
598
564
<pre>sed -i 's/distro = None/distro = YOUR DISTRO NAME' pyradio/config</pre>
599
565
<p>Then you go on to produce the package as you would normally do.</p>
600
566
<p>For example, an <strong>Arch Linux</strong> packager would use this command:</p>
<p>The distro name you insert here will appear in <strong>PyRadio</strong>’s log file, so that I know where the package came from while debugging, so if you are not packaging for a specific distribution, please do use something meaningful (for example, using “<em>xxx</em>” will do the job, but provides no useful information).</p>
568
+
<p>The distro name you insert here will appear in <strong>PyRadio</strong>’s “<em>Configuration Window</em>”. In addition to that it will appear in the log file, so that I know where the package came from while debugging.</p>
569
+
<p>Having siad that, if you are not packaging for a specific distribution, please do use something meaningful (for example, using “<em>xxx</em>” will do the job, but provides no useful information).</p>
603
570
<h2id="todo">TODO <spanstyle="padding-left: 10px;"><supstyle="font-size: 50%"><ahref="#" title="Go to top of the page">Top</a></sup></style></h2>
0 commit comments