SliTaz Repositories

     1.1 --- a/gnumeric/receipt	Wed Oct 28 15:08:46 2015 -0400
     1.2 +++ b/gnumeric/receipt	Wed Oct 28 21:41:59 2015 +0000
     1.3 @@ -27,19 +27,27 @@
     1.4  		--without-gnome \
     1.5  		$CONFIGURE_ARGS &&
     1.6  	make && make install
     1.7 +
     1.8 +	sed -i 's|zz-application/zz-winassoc-xls;||' \
     1.9 +		$install/usr/share/applications/gnumeric.desktop
    1.10  }
    1.11  
    1.12  # Rules to gen a SliTaz package suitable for Tazpkg.
    1.13  genpkg_rules()
    1.14  {
    1.15  	mkdir -p $fs/usr/lib $fs/usr/share
    1.16 -	cp -a $install/usr/bin $fs/usr
    1.17 -	cp -a $install/usr/lib/*.so* $fs/usr/lib
    1.18 -	cp -a $install/usr/lib/$PACKAGE $fs/usr/lib
    1.19 -	rm -rf $fs/usr/lib/$PACKAGE/$VERSION/include
    1.20 -	rm -rf $fs/usr/lib/$PACKAGE/$VERSION/plugins/*/*.la
    1.21  
    1.22 -	cp -a $install/usr/share/$PACKAGE $fs/usr/share
    1.23 -	cp -a $install/usr/share/pixmaps $fs/usr/share
    1.24 +	cp -a $install/usr/bin          $fs/usr
    1.25 +
    1.26 +	cp -a $install/usr/lib/*.so*    $fs/usr/lib
    1.27 +	cp -a $install/usr/lib/gnumeric $fs/usr/lib
    1.28 +	find $fs/usr/lib -name '*.la' -delete
    1.29 +
    1.30 +	cp -a $install/usr/share/applications $fs/usr/share
    1.31 +	cp -a $install/usr/share/glib-2.0     $fs/usr/share
    1.32 +	cp -a $install/usr/share/gnumeric     $fs/usr/share
    1.33 +	cp -a $install/usr/share/icons        $fs/usr/share
    1.34 +	rm -r $fs/usr/share/icons/hicolor/scalable
    1.35 +	cp -a $install/usr/share/pixmaps      $fs/usr/share
    1.36 +	find $fs/usr/share/pixmaps -name '*.ico' -delete
    1.37  }
    1.38 -

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/memtester/description.txt	Wed Oct 28 21:41:59 2015 +0000
     2.3 @@ -0,0 +1,43 @@
     2.4 +memtester is a utility for testing the memory subsystem in a computer to
     2.5 +determine if it is faulty.
     2.6 +
     2.7 +Usage is simple for the basic case. As root, run the resulting memtester binary
     2.8 +with the following commandline:
     2.9 +
    2.10 +    memtester <memory> [runs]
    2.11 +
    2.12 +where `<memory>` is the amount of memory to test, in megabytes by default. You
    2.13 +can optionally include a suffix of B, K, M, or G (for bytes, kilobytes,
    2.14 +megabytes, and gigabytes respectively).
    2.15 +
    2.16 +`[runs]` is an optional limit to the number of runs through all tests.
    2.17 +
    2.18 +An optional `-p physaddr` argument available to cause memtester to test memory
    2.19 +starting at a specific physical memory address (by mmap(2)ing a device file
    2.20 +representing physical memory (/dev/mem by default, but can be specified with the
    2.21 +`-d device` option) starting at an offset of `physaddr`, which is given in hex).
    2.22 +
    2.23 +Note: the memory specified will be overwritten during testing; you therefore
    2.24 +*cannot* specify a region belonging to the kernel or other applications without
    2.25 +causing the other process or entire system to crash). If you use this option, it
    2.26 +is up to you to ensure the specified memory is safe to overwrite. That makes
    2.27 +this option mostly of use for testing memory-mapped I/O devices and similar.
    2.28 +Thanks to Allon Stern for the idea behind this feature. For example, if you want
    2.29 +to test a bank of RAM or device which is 64kbytes in size and starts at physical
    2.30 +address 0x0C0000 through the normal /dev/mem, you would run memtester as
    2.31 +follows:
    2.32 +
    2.33 +    memtester -p 0x0c0000 64k [runs]
    2.34 +
    2.35 +If instead that device presented its memory as /dev/foodev at offset 0, you
    2.36 +would run memtester instead as follows:
    2.37 +
    2.38 +    memtester -p 0 -d /dev/foodev 64k [runs]
    2.39 +
    2.40 +Note that the `-d` option can only be specified in combination with `-p`.
    2.41 +
    2.42 +memtester must run as user root so that it can lock its pages into memory. If
    2.43 +memtester fails to lock its pages, it will issue a warning and continue
    2.44 +regardless. Testing without the memory being locked is generally very slow and
    2.45 +not particularly accurate, as you'll end up testing the same memory over and
    2.46 +over as the system swaps the larger region.