<cruxbridge>
<tim> joe9: consider setting PKGMK_IGNORE_NEW="yes" in /etc/pkgmk.conf
<joe9>
will that make the footprint's out of sync with the system?
<cruxbridge>
<tim> no
<cruxbridge>
<tim> it will ignore NEW files which are generally harmless.
<cruxbridge>
<tim> you should be more concerned about missing files
<joe9>
I have not built CRUX ports in a decade. I am trying to build ports for dahdi and asterisk for 3.7. I found ports for them in 3.4 and 3.5.
lavaball has joined #crux
<joe9>
to update the signature, pkgmk asks me for the security keys.
<joe9>
how do I go about it?
<joe9>
thanks.
<cruxbridge>
<tim> you don't
<cruxbridge>
<tim> the keys are a secret
<cruxbridge>
<tim> you can ignore checking the signature manually, e.g. with pkgmk there is the -is flag
<joe9>
I can. But, I want to update the signature.
<joe9>
I am updating the packages to the latest releases.
<joe9>
so, the files in the Pkgfile change.
<cruxbridge>
<tim> It's not intended to be used that way (if you updated a core/opt/... port). If this is your own repository, you can generate your own key and sign your own ports
<joe9>
at this point, these old ports will be going into my own repository.
<joe9>
as, they are not in contrib anymore.
<joe9>
so, just put them in my local repo and work with them. If all goes well, I can reach out to you to see if you can take them into contrib.
<cruxbridge>
<tim> contrib is not really something you come and load with your ports to have them maintained. The process usually involves you that wants them in contrib to maintain them yourself.
<joe9>
oh, ok.
<cruxbridge>
<tim> Usually, you'd want to make your very own repository public and get it listed on the portdb, and after a while, you can consider applying for contrib if you want to join up
<joe9>
ok, makes sense.
<joe9>
are there any instructions to generate the key to sign my ports.
serpente has quit [Remote host closed the connection]
serpente has joined #crux
<cruxbot>
[core/3.7]: cmake: updated footprint
<SiFuh>
jaeger: That setup-chroot script has a small problem. If you run it more than twice you will find nice issues
<SiFuh>
I have a script that can check if chroot is already run and just run 'chroot' rather than binding everything. You could look at it and maybe tweak the setup-chroot to detect if setup-chroot has already been run.
<jaeger>
Yeah, would be easy to modify it... but out of curiosity, why would you run it more than once?
<SiFuh>
jaeger: A newbie ;-) switching consoles
<SiFuh>
And I meant more than once. Not more than twice.
<jaeger>
Hrmm, fair enough
<SiFuh>
So they can run setup-chroot as many times as they want or chroot directly. The script should detect if it has been run before and accommodate for it.
<jaeger>
Yeah, I get the concept
<SiFuh>
jaeger: I knew did. :-P
<SiFuh>
I knew you did*
brian|lfs has quit [Ping timeout: 248 seconds]
brian|lfs has joined #crux
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux
<joe9>
What command is used to create patch files in a port? diff -u seems to be in a different format.