README.md

@@ -6,7 +6,7 @@ distributions.
  - apt signature and package checksum verification
  - User-level installation
 
-## About
+## Motivation
 Many popular software packages are often distributed as .deb packages, targeting Ubuntu primarily.
 Often they are not available in the repos of others distros. Even if they are, sometimes the version tends to be behind upstream for some time. They may also only be available as "unofficial" packages through user repositories such as AUR, PPA or Gentoo overlays.
 
@@ -18,9 +18,9 @@ The binaries in the .deb actually work on other distributions (often). In fact,
 often use simply fetch the .deb packages from the apt repo in their templates. But they aren't always
 quick to keep their template up to date with the latest upstream version.
 
-There may therefore hardly be a practical benefit in using your distros package manager to install those. Your distro's
-package may essentially just be a "proxy" for the .deb. Although you can make a version bump yourself,
-it is rather inconvenient and you'll have to monitor for new releases yourself. Even though being out
+There is thus hardly a practical benefit in using your distros package manager to install those. Your distro's
+package is just a proxy  for the .deb. Although you can make a version bump yourself,
+it is rather inconvenient and you'll have to monitor for new releases yourself. Although being out
 of date is not a big problem often, it obviously can be when you are missing out on security updates.
 
 debfetcher simply identifies the latest version of a package in the corresponding apt repo, downloads it and then installs the binaries from the .deb.
@@ -35,7 +35,7 @@ debfetcher verifies the repo signatures and .deb checksum (just like apt).
  - You don't have to wait for your distribution to make a version bump
 
 ## Status
-It is, and will most certainly remain, a "hack" (although a useful one for me)
+It is, and will most certainly remain, a hack (although a useful one for me)
 
 ## FAQ
 
@@ -49,7 +49,7 @@ But as said above, this is not my idea.  Using the .deb even for distros not bas
 debfetcher aims to be distro-agnostic.  It will not install any dependencies.
 
 If they are missing, you'll get an error (most likely when starting the app).
-Hence, you will have to make sure that they are installed. The packages debfetcher was tested on bundle some
+Hence, you will have to ensure yourself that they are installed. The packages debfetcher was tested on bundle some
 of their dependencies. Also, in a typical Linux desktop installation chances are you already have all dependencies installed.
 
 
@@ -86,7 +86,7 @@ Note: The config/data directories of the installed packages won't change, which
 problematic.
 
 ## Usage
-### Install/Upgrade a package
+### Install a package
 ```
 debfetcher.sh get [packagename]
 ```
@@ -95,3 +95,9 @@ debfetcher.sh get [packagename]
 ```
 debfetcher.sh upgrade
 ```
+
+
+
+
+
+

packages/element-desktop.debfetcher

@@ -1,26 +0,0 @@
-APTURL="https://packages.element.io/debian"
-DISTRO="default"
-REPO="main"
-PUBKEY="${PUBKEY_PATH}/element-io-archive-keyring.gpg"
-PACKAGE="element-desktop"
-
-TS=$(date +%s)
-THIS_BASEDIR="/opt/Element"
-
-install()
-{
-    #Inspired by Gentoo's ebuild
-
-    cp -a --parents --  opt/Element "${DEBFETCHER_INSTALL_DESTDIR}"
-    cp --parents -- usr/share/applications/element-desktop.desktop "${DEBFETCHER_INSTALL_DESTDIR}"
-    chmod o=r ${DEBFETCHER_INSTALL_DESTDIR}/usr/share/applications/element-desktop.desktop
-    
-    ln -sf ${DEBFETCHER_INSTALL_DESTDIR}/opt/Element/element-desktop "${DEBFETCHER_BIN_SYMLINK_DIR}"
-
-    find usr -name element-desktop.png | while read line ; do
-        path=$(dirname "$line")
-        mkdir -p -- /${DEBFETCHER_INSTALL_DESTDIR}/${path}
-        cp -a "$line" -- ${DEBFETCHER_INSTALL_DESTDIR}/${path}
-    done
-}
-