Open scsijon opened 4 years ago
This seems pretty easy to add. Do you want to try to write the build rules yourself or wait for someone to pick it up?
On 03/03/20 05:03, Dmitry Golovin wrote:
This seems pretty easy to add. Do you want to try to write the build rules yourself or wait for someone to pick it up?
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/tpimh/nenuzhnix/issues/52#issuecomment-593535574
Sorry, but can I leave things up to others please at present as at the moment i'm heavily involved with T2 for a month or six weeks still, I'm just adding what I think usefull and I think missing items into the packageset while I remember to do so. I've a couple of others, but I want to do further investigation first.
thanks scsijon
Just a note that i'm finally back. (phew).
I shall have a look at the rules used for the other packages already done and see if I can do it myself before yelping unless someone is already having a go.
I want to get my EasyOS development system cleaned out/updated/refreshed first and build the basic nenuzhnix system before getting into it though, so i won't be starting on this for a week.
I've got a few others that i've thought of or come across that may be of interest after refreshing myself to see if their addition and usefull is to add at this stage of nenuzhnix's development.
I haven't updated the packages in a while, so really hope to see bim in next nenuzhnix release!
OK, first problem is how do I update my fork from your base (not having done that before),or is it easier to delete my existing fork and start again? Since there are a few of the other packages that also need updating, so I might as well as do that first before downloading a copy and starting things rolling in my fork with bim.
On 30/9/20 7:38 pm, Dmitry Golovin wrote:
I haven't updated the packages in a while, so really hope to see bim in next nenuzhnix release!
I guess, it would be easier to start over at this point. Last release was over a year ago, so there must be many outdated packages, I had a handy script to check the latest versions for all packages, hope I can find it. If you can help keeping packages up to date, that's great! Usually, you will just need to change the version number and the checksum of the package, but sometimes might be tricky.
Um, what source format tarballs do 'we' use? I looked at some packages and the .gitignore makes me think your using .zip. I just want a confirmation as there are quite a few needing updates.
And MD5 is dangerous , as it's been found to be easy to 'fudge', maybe consider moving to sha224sum in the near future.
I've created a rough bim, but have not yet uploaded it as it's still incomplete and i want to create a up-to-date base first.
On 28/10/20 9:08 pm, Dmitry Golovin wrote:
Assigned #52 to @scsijon.
For source tarballs .tar.gz
, .tar.bz2
and .tar.xz
are currently supported, so for bim correct variables should be the following:
Repo: https://github.com/klange/${PKG}/archive/
Filename: v${VER}.tar.gz
MD5: 7b3fdd0025726295f0387d7f5c358a34
MD5 here is only used to check the integrity of the source, so to me it seems very unlikely that someone hacks software repositories adds malicious code to the source and then 'fudges' source tarballs to have the same MD5 sums. Still, it's very easy to change it to SHA224.
Also in case you don't know, there is a guide on adding new package: https://github.com/tpimh/nenuzhnix/wiki/add-a-package
Feel free to comment and extend it.
No I didn't, and a quick look at it against what i had done, I did crap!
I'll start again on the weekend as i'm a !bit busy at present.
On 12/11/20 2:27 am, Dmitry Golovin wrote:
Also in case you don't know, there is a guide on adding new package: https://github.com/tpimh/nenuzhnix/wiki/add-a-package
Feel free to comment and extend it.
Hi @scsijon! I've been updating the packages and also tried to build bim. Version 2.6.2 was build without any warnings and here are my versions of the build files, feel free to use them:
rules
:
#!/bin/sh
set -e
PACKAGE=bim
case "$1" in build) make ;;
install) rm -rf /tmp/$PACKAGE mkdir -p /tmp/$PACKAGE DESTDIR=/tmp/$PACKAGE make install DESTDIR=$DESTDIR ;;
clean) make clean ;;
*) echo unknown argument $1 ;; esac
- `source`:
Repo: https://github.com/klange/${PKG}/archive/ Filename: v${VER}.tar.gz MD5: 2f408810ec7038694d93fc2755291958
- you will also need to create `control` file, it's pretty easy and is described in wiki, but if you will have troubles with it, feel free to ask
https://github.com/klange/bim/ Bim has no external dependencies beyond a functioning C library, C99 compiler, and sufficient escape code support in the hosting terminal.