Blendie has quit [Quit: Connection closed for inactivity]
mishima has quit [Ping timeout: 480 seconds]
<pairisto[m]>
PulkoMandy: do you think if we just work on the `kernel/drivers/network/tun/driver.c` itself since it might be easier to change the linux related code to haiku related code? As far as I am aware we would need to take the Bone related stuff out of it because haiku doesn't use Bone?
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
jbehnke747 has joined #haiku
jbehnke747 has quit []
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
Maturi0n has joined #haiku
mishima has joined #haiku
Maturi0n_ has quit [Ping timeout: 480 seconds]
mishima has quit [Ping timeout: 480 seconds]
mmu_man has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
bbjimmy_64 has quit [Quit: Vision[]: i've been blurred!]
<pairisto[m]>
Also should I just port over a VPN product like wireguard and reverse the driver that it wants?
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
AlienSoldier has quit [Quit: Vision[]: i've been blurred!]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
Kokito has joined #haiku
Kokito has quit [Quit: Vision[]: i've been blurred!]
mishima has quit [Ping timeout: 480 seconds]
dairyhungWL has joined #haiku
mishima has joined #haiku
dairyhungWL has quit [Ping timeout: 480 seconds]
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
<pairisto[m]>
from what I know, there needs to be a tun driver for VPNs specifically if I am going off of linux for reference but I could look more into what something like wireguard needs to work and work backwards to porting it from there
<PulkoMandy>
Yes, making the driver provige what wireguard expects seems good. I don't know how our network stack internals differ from Bone to decide if there is something worth reusing in that driver
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
mishima has joined #haiku
Begasus has joined #haiku
<Begasus>
g'morning peeps
* OscarL
yawns.
<OscarL>
hi Begasus!
mishima has quit [Ping timeout: 480 seconds]
<Begasus>
hi OscarL !
<Begasus>
saw your comments, will address and look at them in a bit, first the dogs in about 10 minutes :)
<OscarL>
np. I will most likely be sleeping in a shot while :-)
<OscarL>
Enjoy the dogs!
<Begasus>
Will do :)
<Begasus>
sending them outside, a bit of play and then the younger ones into the kennels, and the 2 old ladies in the house :)
<Begasus>
oh, and some fresh coffee to make (got one from yesterday but that's cold by now) :)
<Begasus>
already took my breakfast (9 pills) and a sandwich :D
<Begasus>
you didn't remove the 3.7 and 3.8 versions?
mishima has quit [Ping timeout: 480 seconds]
<OscarL>
Can't recall right now if I checked for dependencies for the packages on my PRs. Sorry. 5 AM here :-(
<OscarL>
Last I did was checking some of yours, and only commented on the ones that was relatively easy to determine if could be removed or not.
xet7 has quit [Quit: Leaving]
xet7 has joined #haiku
<OscarL>
Begasus: seems that for importlib_resources we could remove 3.7 and 3.8, if we do the same for alembic. gertty depends on the later, and alembic depends on importlib_resources. But gertty is Py 3.9+ already.
Blendie has joined #haiku
mishima has joined #haiku
<Begasus>
I did some major work on the python recipes (bumping versions) some years ago, you could do the same as you are our python guy now :P
<OscarL>
Guido van Rossum would faint if he finds out :-)
<pairisto[m]>
does anyone have any tips when working on porting an application over to haiku?
<Begasus>
deppends on what you want to do, external applications end up in haikuports
<Begasus>
quite some documentation there on the wiki
<pairisto[m]>
porting wireguard in particular
<Begasus>
maybe you could look into the recipe for wireshark? (not sure if they are related though) :)
<Begasus>
does it build in Terminal?
<pairisto[m]>
I believe it does, at least in linux it does/can, but it isn't quite related to wireshark though that recipe will still probably be helpful either way
<Begasus>
for new stuff I usaly look if they can be build in Terminal first
<Begasus>
you could hit missing deppendencies
<Begasus>
it also helps you understand if a package is available but not found (usaly a missing develop package that can be installed with pkgman in Terminal)
<pairisto[m]>
any particular steps after you have the dependencies or is it mostly just various kinds of trouble shooting from there?
<OscarL>
that's why I ealier wrote: "Ah... these rookie guys, always forgetting something, right Begasus? :-P"
<Begas_VM>
ah :D
<Kokito>
Hi Begas_VM!
DKnoto has joined #haiku
<OscarL>
Begas_VM: so... seeing that you went and killed support for 3.7/3.8 for some pytest dependencies... guess I should do the same for pytest now?
<botifico>
[haikuports/haikuports] OscarL ef3df7a - pytest_relaxed: drop support for Python 3.7 and 3.8. (#8013)
<Begasus>
Hi david
matt1 has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
<OscarL>
Question Begasus... asciidoc has pytest_python3 in its TEST_REQUIRES (but python 3.9 for the rest of the recipe, LOL). As this would be a chage only for TEST... guess we don't need a rev-bump?
<OscarL>
(I mean.... the change won't be "user-facing", and as the buildmaster doesn't runs tests...)
<matt1>
python xD
<matt1>
Jesus is stronger ... i apologize but true ... :)
<Begas_VM>
hi matt1, please no relegion here
<matt1>
xD
matt1 has left #haiku [#haiku]
<OscarL>
that was quick.
<Begas_VM>
if nothing else changes OscarL?
<Begas_VM>
;)
mishima has joined #haiku
<OscarL>
no other change, no.
<Begas_VM>
sorry, but this is not the place for that (imho)
<Begasus>
probably could be dropped, I think because was looking for both pkg-config and cmake (that also provides config files)
<Habbie>
oh right
<Habbie>
yes pkg-config seemed to cover that
<Begasus>
yep, and I don't think inih provides any cmake config files
<Begasus>
let me check the packages
CPYou has joined #haiku
mishima has quit [Ping timeout: 480 seconds]
<Habbie>
i crashed my haiku by unplugging a usb stick
<Habbie>
indeed, .pc in inih_devel but nothing for cmake
<Begas_VM>
yep, can be dropped, my bad ;)
<Habbie>
will do
<Habbie>
the ninja dep is silly too, but fixing that requires some work on haikuporter
<Habbie>
wait i mean the meson dep
mishima has joined #haiku
<Habbie>
rephrase, the mix of calling meson and ninja in the recipe is haikuporter silliness, we might in fact need both deps
<zdykstra>
I wonder how obnoxious it's going to be to debug why imap connection workers sometimes 'break' and I have to restart mail_daemon to get mail again for an account
CPYou has quit [Quit: Lost terminal]
mishima has quit [Ping timeout: 480 seconds]
bbjimmy_64 has joined #haiku
mishima has joined #haiku
CPYou has joined #haiku
<Begas_VM>
I don't think you can leave ninja out
<Habbie>
that we have to explicitly call ninja is, in my opinion, a haikuporter bug
<Habbie>
but we'd probably still need the dep when that bug is fixed, yes
<Begas_VM>
isn't it possible to build meson packages without ninja? (meson --build build ...)
<Habbie>
that calls ninja
<Habbie>
but also you can't do it in haikuports
<Begas_VM>
right
<Habbie>
because haikuporter checks meson arguments
<Begas_VM>
well, somehting for you, I'm in the blue there ;)
<Habbie>
assuming all meson calls are that first 'build' call
Blendie has quit [Quit: Connection closed for inactivity]
<Begasus>
they all provide devel:liblua
<Begasus>
makes sure it is compatible with the base package
<Begasus>
mostly not needed
<Begasus>
k, done for today, calling it a night
<OscarL>
sleep well Begasus!
<Begasus>
g'night peeps!
Begasus has quit [Quit: Leaving]
mishima has quit [Ping timeout: 480 seconds]
<OscarL>
Our ports/packages may have rought edges, but considering how few people actually run the show... I find it quite impressive!
<B2IA>
(Butler) Welcome to BeShare.agmsmith.ca.
<B2IA>
Oops, forgot to turn off IRC when rebooting the server, sorry for the noise.
mishima has joined #haiku
jmairboeck has joined #haiku
cocobean has joined #haiku
<Habbie>
OscarL, definitely agreed!
<Habbie>
the lua thing i mentioned is, specifically, the kind of thing that won't come up with "just a few" users
<Habbie>
and haikuporter is super slick
mishima has quit [Ping timeout: 480 seconds]
<Habbie>
oh no
<Habbie>
i was going to port vis
<Habbie>
which wants libtermkey
<Habbie>
libtermkey is managed in a bazaar repo
<Habbie>
bzr is so old it uses python2, so haikuports now installed python2
<Habbie>
and now i feel i need to port brz too ;) (bazaar's successor)
<OscarL>
haha, been there WAY too many times.
<Habbie>
but, i'll skip that for now, termkey has tarballs
<OscarL>
old ass python versions keep appearing on my system despite me nuking them when I see them :-D
<Habbie>
:)
<Habbie>
ok, uninstalled
<OscarL>
maybe running haikuporter without "--get-dependencies" could help at first to gauge what the dependencies will look like? (I'm assuming it will complain about the missing ones in that case)
mishima has joined #haiku
<Habbie>
you mean for my surprise python2 install?
<OscarL>
yea :-)
<Habbie>
that was pkgman, which asked nicely :)
<Habbie>
so
<Habbie>
should a port every -not- use $secondaryArchSuffix?
<Habbie>
on one hand, sometimes it's pointless
<Habbie>
on the other hand, i might later discover i needed it
<Habbie>
and "pointless" is not "bad" in itself
<OscarL>
guess you could just leave it in, disabled (?x86 for example), and let the reviewers yell at you if they disagree :-D
<Habbie>
ack!
<Habbie>
?x86_gcc2 i'm guessing, mostly
<OscarL>
that one too, unless you personally tested it.
<Habbie>
right
<OscarL>
(but that's a PRIMARY arch=
<OscarL>
s/=/)/
<Habbie>
oh right
<Habbie>
haven't gotten the hang of it yet
<Habbie>
ok so what would the ARCH vars look like for "i have only tested this on x86_64" ?
<OscarL>
its confusing at first, specially if you, like me, assume that .recipes are all 100% perfect examples (there are many left overs)
<Habbie>
hehe yes
<Habbie>
been bitten by that in many OSes
<Habbie>
slash projects
<OscarL>
ARCHITECTURES="all ?x86_gcc2"
<OscarL>
SECONDARY_ARCHITECTURES="?x86"
<Habbie>
oh right
<Habbie>
and ? makes 'hp' build it but the real builder skip it, right?
<OscarL>
it will build it for you locally, depending on your hp .conf