- Timestamp:
- 07/07/2020 12:42:50 PM (3 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, ken/inkscape-core-mods, lazarus, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226
- Children:
- 9e2a8bab
- Parents:
- b2bd6604
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
gnome/platform/gjs.xml
rb2bd6604 r9621162 7 7 <!ENTITY gjs-download-http "&gnome-download-http;/gjs/1.64/gjs-&gjs-version;.tar.xz"> 8 8 <!ENTITY gjs-download-ftp "&gnome-download-ftp;/gjs/1.64/gjs-&gjs-version;.tar.xz"> 9 <!ENTITY gjs-md5sum " e25ca40cd2c1b88e4778ddb6bb7f4d64">10 <!ENTITY gjs-size "41 6KB">11 <!ENTITY gjs-buildsize " 273MB (with tests)">12 <!ENTITY gjs-time "0. 6SBU (with tests)">9 <!ENTITY gjs-md5sum "dc0d4a0453484c5a77eb0e2bda091704"> 10 <!ENTITY gjs-size "413 KB"> 11 <!ENTITY gjs-buildsize "65 MB (with tests)"> 12 <!ENTITY gjs-time "0.2 SBU (with tests)"> 13 13 ]> 14 14 … … 102 102 <sect2 role="installation"> 103 103 <title>Installation of Gjs</title> 104 104 <!-- 105 105 <para> 106 106 First, work around a bug in meson caused by support for Windows NT: 107 107 </para> 108 108 109 <!--When scripting, 'ninja install' fails because the 'gjs' symlink is109 When scripting, 'ninja install' fails because the 'gjs' symlink is 110 110 generated before 'gjs-console' is installed. This seems to be due 111 111 to adding symbolic link support for Windows NT-based platforms. … … 113 113 like we do in other packages. 114 114 Invalid with 1.64.3. Make sure you don't have DESTDIR 115 set, such as you'd do in an update script. -->116 117 < !--<screen><userinput remap="pre">sed -i '/symlink-gjs.py/s/^/#/g' meson.build</userinput></screen>-->115 set, such as you'd do in an update script. 116 117 <screen><userinput remap="pre">sed -i '/symlink-gjs.py/s/^/#/g' meson.build</userinput></screen>--> 118 118 119 119 <para> … … 131 131 To test the results, issue: <command>ninja test</command>. The 132 132 <application>GTK</application> and <application>Cairo</application> 133 tests will fail if not running in an Xorg session. One test, 133 tests will fail if not running in an Xorg session. 134 <!-- All 53 tests passed for me with gjs-1.64.4 135 One test, 134 136 <filename>gjs: Scripts/CommandLine</filename>, is known to fail. 135 On some systems, up to six tests may fail with an error. 136 <!-- Still fails with 1.58.5. --> 137 On some systems, up to six tests may fail with an error. --> 137 138 </para> 138 139
Note:
See TracChangeset
for help on using the changeset viewer.