dont store packages by deeper category

packages/filesystem/filesystem.make

@@ -0,0 +1,12 @@
+SUBDIRS = $(shell ls -d */)
+
+all:
+    for dir in $(SUBDIRS) ; do \
+        make -C  $$dir ; \
+    done
+
+
+clean:
+    for dir in $(SUBDIRS) ; do \
+        make clean -C  $$dir ; \
+    done

packages/filesystem/fonts/font-source-code-pro/src/debian/install

@@ -1 +0,0 @@
-*.ttf usr/share/fonts/truetype/source-code-pro-ttf

packages/packaging-readme.md

@@ -16,7 +16,7 @@ When an existing PrawnOS install has out of date packages, the user can then eit
 build the new version themselves or get the update from the repo using the standard "apt upgrade"
 
 ### Package folder structure
-Packages are stored under component of the final PrawnOS image they belong to, and then for filesystem packages, the component of the filesystem they belong to. 
+Packages are stored under component of the final PrawnOS image they belong to
 Inside the package folder there are the following items:
 - `makefile`
 - source folder called `src`

scripts/buildFilesystem.sh

@@ -62,7 +62,7 @@ build_resources=resources/BuildResources
 # unstable as well, but that conflicts with some of the gnome packages it seems. Luckily, we can now build xsecurelock
 # for buster instead of grabbing it from unstable.
 # I'm rethinking the build system to make (heh) this more elegant, but for now to get the build fixed I'll implement this
-XSECURELOCK_PATH=packages/filesystem/x11/xsecurelock
+XSECURELOCK_PATH=packages/filesystem/xsecurelock
 
 #A hacky way to ensure the loops are properly unmounted and the temp files are properly deleted.
 #Without this, a reboot is sometimes required to properly clean the loop devices and ensure a clean build