Open ehawman opened 2 years ago
dmacias72
commented
2 years ago Those instructions are for creating a slackware package for a plugin. Putting any binaries and webui pages from the SRC directory into a compliant installable slackware package with a date as the version number and modifies the plugin plg file with the package name.
dmacias72
commented
2 years ago The binary packages I personally compile for unraid I do so in a VM with the latest version of unraid. I install my DevPack plugin which contains the headers that they remove from unraid for the binaries that are built in. DevPack also includes many of packages necessary for compiling.
So first you need a VM or a install of unraid. I don't recommend your main install of unraid. But you could use it and the reboot once you're done. You need to create a build directory on you flash drive of the VM or unraid you're using to compile. Next install DevPack. Then you need to go to slackbuilds.org and search for the package you want to compile. In this case micro. I only saw a slackbuild for slackware 15 but it should work. You need to download the micro.tar.gz slackbuild file and extract it into the build directory you created on your flash drive in its own directory micro. (not sure if the slackbuild file has paths built in) It contains the micro.Slackbuild file which is the script to compile micro. I edit the Slackbuild file to output txz instead of tgz. Next you can download the source from slackbuild or the linux 64 source from github. You need the tar.gz format. Place that in the build/micro. Next you ssh into the vm and go to build/micro. The run sh micro.Slackbuild and see what errors or headers it complains about. Maybe you'll get lucky and it will compile. It will create the package in /tmp. You need to move that to your flash drive or somewhere other than temporary memory.
ehawman
commented
2 years ago @dmacias72 thank you very much for the writeup. That clears a ton of things up.
My understanding of Unraid licensing is that starting the array requires a paid license, while booting into the OS shouldn't require anything. I'm unsure if I can install DevPack to an unlicensed Unraid install, but I'll look into it tonight. Perhaps I can install it on a trial then continue using it afterwards?
I've done a quick writeup here which documents my understanding of what you've written. Please correct me where I've gone astray. I'm missing pkg_build.sh and sudo ./mkpkg plugin in here as I'm not 100% sure where they come in.
Environment Setup:
/boot/package_builds/Build Package:
PKGTYPE=${PKGTYPE:-tgz} to `PKGTYPE=${PKGTYPE:-txz}cd /boot/package_builds/micro./micro.SlackBuildcp -r /tmp/????.txz /boot/package_builds/micro/result/????.tzxPrepare Git Pull Request:
micro-2.0.10????.txz to /packages/[version-of-your-Unraid-VM]/
scp root@yourunraidserver:/domains/unraid_build_vm_example_volume/boot/package_builds/micro/result/????.tzx /path/to/git/folder/unRAID-NerdPack/packages/6.10/????.tzxAgain, thank you for taking the time out to assist me with this. Hopefully I can pay it forward.
dmacias72
commented
2 years ago Looks like you got it. The pkg_build.sh and mkpkg were only for creating packages for plugins. When I make a change to the NerdPack or other plugin I use them to create the new plugin package. I also forgot, you need to edit the micro.Slackbuild file and make changes at the top of the file to point to the new version of source if it's different. You don't need to extract the micro source either. Just place the micro-2.0.10-linux64.tar.gz in the same directory as micro.Slackbuild.
While I have a couple unraid licenses, I never went through the process of setting up the VM using a second USB stick because at the time have 2 unraid usb sticks when booting wouldn't work constantly. Maybe the option to select the main boot USB wasn't complete yet. Now I think you can pick a particular USB to boot from and it will work. So I boot the VM with a virtual image. Can't remember if I just cloned my main usb or not. You are correct you can't start the array and unraid will complain about the invalid license. But you can install plugins and compile all you want. I just make copies of the virtual drive and upgrade so I can have multiple copies and run different versions.
You can just do a pull request on the main branch. Just place the package in the correct unraid version directory. Also you can add the source slackbuild files under src like I've done for some packages.
Also thanks very much for trying to do this. I just don't have much time anymore and rarely get on the forums.
ehawman
commented
2 years ago @dmacias72 Sweet. Ok Take II
Environment Setup:
/boot/package_builds/Build Package:
PKGTYPE=${PKGTYPE:-tgz} to PKGTYPE=${PKGTYPE:-txz}VERSION=${VERSION:-2.0.10}cd /boot/package_builds/micro./micro.SlackBuildcp -r /tmp/micro-2.0.10.txz /boot/package_builds/micro-2.0.10.tzxPrepare Git Pull Request:
Main branch.micro-2.10.0yourpackage.txz from the Unraid VM to the fork on your local machine, in /packages/[version-of-your-Unraid-VM]/
scp root@yourunraidserver:/domains/unraid_build_vm_example_volume/boot/package_builds/micro-2.0.10.tzx /path/to/git/folder/unRAID-NerdPack/packages/6.10/micro-2.0.10.tzxscp -r root@yourunraidserver:/domains/unraid_build_vm_example_volume/boot/package_builds/micro/ /path/to/git/folder/unRAID-NerdPack/source/SlackBuild/micro/I left the creation of a new branch branch management in there since A) It's best practice and B) it can really help compartmentalize things should someone be working on multiple different packages at a time (which people will definitely be doing since it makes sense to build 5 packages on the particular version of Unraid currently installed before moving to the next one vs cycling through versions X times per package, 5 different times)
Unfortunately I ran out of time to test the VM (and the whole process) but I should be able to carve some time out tomorrow. Believe me, I know the horrific burden of discovering I've signed up for a forever task. Hopefully these instructions will allow absolutely anyone to build packages, meaning your job will just be to glance over/approve the pull requests and do periodic package updates.
If you care to peel back the curtain a bit more on what happens when my instructions end, perhaps there's some more automated releasing that can be done. I have less than zero knowledge about how releasing plugins to Community Apps works, but walk me through it and maybe we can completely automate the process.
Heck, how sweet would it be to feed a script the URL to download the source tar.gz, the SlackBuild tar.gz, and then sit back and let it crank out 15 different packages for 15 different Unraid versions, and finally push the entire shebang to the Community Apps store?
dmacias72
commented
2 years ago It sounds great. For Community apps, I believe you have to create a repo with xml files pointing to the plugin repos. Community apps polls the repo for changes. Nerdpack just polls the packages repo for changes. So if you update a package, once it's pages to github, it will show up in unraid's webui. When you mentioned before about branches it got me thinking that all the packages should be separated out into their own repo for unraid packages. Then have different branches for different version of unraid. Nerdpack repo should just be for code changes. I really never add packages to older versions. Most people are either on the latest or version just before or testing the next version.
ehawman
commented
2 years ago Ok well I had a beautiful dream but I keep stepping on a rake at Stage 1.
I cannot, for the life of me, get an Unraid VM working on a Windows or Mac machine. And that's using every human-flexible trick at my disposal, not even trying to script the process.
How did you build your VM?
dmacias72
commented
2 years ago I run my Unraid VMs on unraid. I followed some guide on the forum a long time ago but here's a link to a guide I just found. https://docs.ibracorp.io/virtual-unraid/
Edit: You don't necessarily have to run all this in a VM. But you run the risk of data loss if you install the wrong package and the server locks up or you manually have to shut down. If you did run it on a regular server, I would just recommend disabling all the devpack packages and restarting when done.
GHTGXL
commented
2 years ago After try a few hours later.
I mostly know what to do,but the package I make still need redo.
OK, The first one is I using ubuntu, so maybe some can use?
Second, I try use dev tools in unraid, but I try to make borg package in unraid, missing openssl. So cant make package. Even I check openssl version, and cli have show the version.
So I swap to ubuntu, See Readme say copy makepkg to /sbin/makepkg. I find makepkg also in /sbin/makepkg in unraid, Copy this to /sbin/makepkg in ubuntu, Also change Chown(owner and group) to root in ubuntu. and change chmod in mc.
on: read by owner, write by owner, execute/search by owner, read by group, execute/searchby group, read by other, execute/searchby other.
I follow SlackBuild>download the build I want>follow https://github.com/dmacias72/unRAID-NerdPack/issues/66#issuecomment-1147748311 >Run xxx.slackbuild> get xxx.txz
But I only get xxx.txz, not have md5, and the package still need redo. Because it still don't working. And size is strange, from nerdpack is 4.2MB, from me is less for 1MB.
Who Know how to fix this?
VergilGao
commented
2 years ago After try a few hours later.
I mostly know what to do,but the package I make still need redo.
OK, The first one is I using ubuntu, so maybe some can use?
Second, I try use dev tools in unraid, but I try to make borg package in unraid, missing openssl. So cant make package. Even I check openssl version, and cli have show the version.
So I swap to ubuntu, See Readme say copy makepkg to /sbin/makepkg. I find makepkg also in /sbin/makepkg in unraid, Copy this to /sbin/makepkg in ubuntu, Also change Chown(owner and group) to root in ubuntu. and change chmod in mc.
on: read by owner, write by owner, execute/search by owner, read by group, execute/searchby group, read by other, execute/searchby other.
I follow SlackBuild>download the build I want>follow #66 (comment) >Run xxx.slackbuild> get xxx.txz
But I only get xxx.txz, not have md5, and the package still need redo. Because it still don't working. And size is strange, from nerdpack is 4.2MB, from me is less for 1MB.
Who Know how to fix this?
here is my script named libsbc.SlackBuild to build libsbc for unraid
#!/bin/bash
PRGNAM=libsbc
SRCNAM=libsbc
VERSION=1.5.1
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
COMMIT=909a9bdf7ab143e1f0baaf9736baebd3cd79aacf
SOURCE=https://git.kernel.org/pub/scm/bluetooth/sbc.git/snapshot/sbc-$COMMIT.tar.gz
CWD=$(pwd)
OUTPUT=${OUTPUT:-$CWD/out}
PKG=${PKG:-$OUTPUT/$SRCNAM}
DESTDIR=${DESTDIR:-$PKG/dest}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i586 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
else
echo -e "not support arch $ARCH"
exit 1
fi
set -e
mkdir -p $OUTPUT $PKG
rm -rf $PKG/*
wget -O- $SOURCE | tar xz -C $PKG --strip-components 1
cd $PKG
chown -R root:root .
find -L . \
\( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
-o -perm 511 \) -exec chmod 755 {} \; -o \
\( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
autoreconf --install
mkdir -p build && cd build
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
../configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--build=$ARCH-slackware-linux
make -j$(nproc) && make install DESTDIR=$DESTDIR
cd ..
mkdir -p $DESTDIR/usr/doc/$PRGNAM-$VERSION
cp -a COPYING COPYING.LIB README $DESTDIR/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $DESTDIR/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
cd $DESTDIR
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-txz}Everything works fine except that the md5 is not generated
Howdy! I want to help create packages myself but I'm struggling with the instructions. I'm not familiar enough with the process to understand why certain things are being done, so I'm having trouble translating them to a different environment. Please bear with me as my questions will likely look like someone fumbling in the dark.
I'm using a Mac machine, but ultimately I think it would be beneficial to have the instructions cover all OSes. I'd be happy to walk through this process on multiple machines and really iron out the instructions so anyone can follow.
The first package I'd like to create is for micro so let's use that as an example. Currently I can install it on Unraid with:
For this operation, I'm assuming I should download the source code from their releases page, which I've done and I have unzipped in
~/example/micro-2.0.10. Or am I taking a built/installed executable and zipping that into a package? Should I be using the/usr/bin/microfrom my Unraid server directly?copy tar-1.13 from unRAID to /bin/tar-1.13 on laptop
Is this used by
makepkg? Is it referencingtar-1.13or justtar? Will any version do or does it have to be1.13?Both Mac and Windows support tar natively, and I believe this is true of 99% of Linux distros as well. Can this step be eliminated entirely?
copy makepkg from unRAID to /sbin/makepkg on laptop
Mac locks down
/sbin/quite thoroughly. You can get to it but it requires rebooting into a special safe mode. I putmakepkgin/usr/local/bin/and it appears on my PATH. Should that be enough?I modified gfjardim's pkg_build.sh to take an argument and add arch type plus modified the lettering function
Is this strictly for reference or should I be doing something with
pkg_build.shat this point? Presumablypkg_build.shshould be somewhere specific, but where? The only one in this repo is/source/SlackBuild/rmlint/pkg_build.sh. Is that right? Should I invoke it somehow?To compile the packages for unRAID plugin run from the source directory
sudo ./mkpkg pluginThis creates a slackware compliant package and md5 in the archive directory with the date as the version number
And adds the date to the plugin file in plugins directory.
e.g.
plugin-2017.06.09-x86_64-1.txzandplugin-2016.06.09-x86_64-1.md5Oh boy here we go. What is
the source directoryin this context? Is it~/example/micro-2.0.10?sudo ./mkpkg pluginpredictably says that./mkpkgcan't be found. For grins I tried it withsudo makepkg microand it saidERROR: Package extension .micro is not supported. I put my executable in/source/, ransudo ./mkpkg microand it dumped an empty.txzin/archive/along with anmd5.At this point I'm pretty stumped. I'm sure the instructions are complete if you have enough familiarity with this kind of thing, but as you can tell I'm clearly missing the important stuff. Please help :)