xet7_ has quit [Remote host closed the connection]
vdamewood has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mmu_man has joined #haiku
Guest14842 has left #haiku [#haiku]
Guest14842 has joined #haiku
nephele has joined #haiku
Begasus_32 has joined #haiku
dovsienko has joined #haiku
<nephele>
waddlesplash: around? :)
<nephele>
I'm sitting at the wine port and have some questions
<x512[m]>
I am related to Wine port and have some answers...
<nephele>
x512[m]: I'm working on seeing what is uptreamable, according to the coding guidelines they don't like ifdefs scattered around (understandably), so taking one issue at a time. First one was termios cs5 cs6 cs7 beeing defined all as 0x0
<nephele>
and if that is fixable in haiku
<x512[m]>
UNIX/POSIX headers have a lot differences in Linux/FreeBSD/OpenBSD/Solaris/Haiku etc..
<x512[m]>
Some of #ifdef __HAIKU__ are absolutely unavoidable.
<nephele>
Some of them, sure. But we should minimize them as much as possible
<nephele>
and if it turns out haiku is wrong or wierd we can fix it
<nephele>
In this case them all having the same value means they fail if they are in a case: statement with warnings enabled, which is th case for the wine port :)
<nephele>
and the header mentions this is a bad idea also
<dovsienko>
to discuss POSIX properly, it takes to spell which specific version you mean, because there are several
<nephele>
dovsienko: in this case, it does not matter that much. wine is a codebase that targets a *lot* of posix systems, so they are already trying to be portable to difference between posix versions
<dovsienko>
what seems to be the problem you are trying to solve?
<nephele>
severall? making the wine port upstreamable :D
<nephele>
This specific case is CS5 CS6 and CS7 from termios.h all declared as 0x0, with wine using all of these properly and this issuing a compiler error for duplicate cases
<x512[m]>
Existing termios.h values can't be changed because of ABI compatibility. c_cflag is 16 bit and 15 bit seems already allocated.
<nephele>
our header sais only 7 and 8 bit are supported, so CS7 and CS8 seem useable to me
<x512[m]>
Side note: New Wine versions can be run with Wayland. linux/input.h is needed to be copied from Linux as many other projects using Wayland.
<nephele>
is there something wrong with your backend?
<x512[m]>
Porting winehaiku.drv to latest Wine need some effort because internal API changed a lot.
<nephele>
Okay. So porting changes. That is fine, I think. The patchset needs to be ported and cleaned up anyway
<x512[m]>
Also networking is broken in latest Wine for unknown reason.
<nephele>
wayland still has the problem that some stuff wine needs is not really suppored
<x512[m]>
nephele: You have contact with Wine developers? Any chances to upstream winehaiku.drv that in prohibited C++?
<nephele>
I don't get where you got that from x512, the coding guideline don't say anything about that, and yesterday in #winehq (on libervia) I was told the Mac driver also uses Objective C
<nephele>
x512[m]: from the patchset, do you think we can create a ticket that list all POSIX problems that we should fix for wine?
<nephele>
to make it easier to port on the nightly branch
<x512[m]>
It is possible to create issue with checklist in HaikuPorts GitHub. It is technically unrelated to core Haiku.
<nephele>
Nah, if it's posix issues this can live on trac
<nephele>
anyhow, i would prefer trac since I don't have a github :)
<x512[m]>
Many of them can be fine from POSIX spec perspective..
smalltalkman__ has joined #haiku
<x512[m]>
It is better to build Wine with Wayland and not X11 until winehaiku.drv is ported.
<nephele>
I don't mind what you put into haikuports right now, I want to work on getting this to be a proper port :)
<Begasus[m]>
haven't really tackled that x512 :)
<Begasus[m]>
update on rust would be more welcome :)
<nephele>
x512[m]: porting winehaiku.drv to the newer version would be good though
<nephele>
would make upstreaming more effective, that we can demonstrate that we can support the driver too
<dovsienko>
nephele: does POSIX say CS5 must be different from CS6 from CS7?
<nephele>
Not explicitly, no.
<nephele>
But the compiler warning does not care if this is legal under POSIX
<dovsienko>
then the fact other OSes define these differently is not a valid grounds to write code that assumes these to be different, I would use a starting point
<dovsienko>
i.e. it may be WINE code incorrectly relying on what is purely a coincidence
<nephele>
We don't support CS5 opr CS6. If there is a POSIX feature flag for this we *can* use this. Sure, but other than that it seems unreasonable to support these be the same value
bjork1intosh has joined #haiku
<nephele>
is there a poisix feature flag? If so I can submit this, hide the CS5 and CS6 case for wine, and that should be fine and dandy
<dovsienko>
if that's the case, then the compiler rejecting duplicate cases in a switch block is just a symptom
<dovsienko>
it certainly demands some closer attention to the switch block to understand what it does
<nephele>
maybe the posix wizard phschafft has some ideas :)
<nephele>
dovsienko: oh it only sets up that the next thing it does takes 5/6/7 bits...
<dovsienko>
it has been a while since I did any serial port driving in C, but let me have a look
<Begasus[m]>
x512: for using wayland on wine I only got as far as: configure: error: Wayland 64-bit development files not found, the Wayland driver won't be supported
<x512[m]>
Can be defined as CS5 = 0x8000, CS6= 0x8020.
<Begasus[m]>
eeps, thought I had those covered in the recipe :)
<dovsienko>
Begasus[m]: if Haiku supports 8 bit only, then the first change ought to disable CS5, CS6 and CS7 rather than CS6, CS7 and CS8, I guess
<dovsienko>
also to have the first change upstream it would help to add a comment why these cases do not exist on Haiku
<x512[m]>
7-8 bits are supported.
<dovsienko>
that's just the tip of the iceberg, that's a 6000 lines patch
<nephele>
x512[m]: okay. That sounds good, let me whip up a patch
<nephele>
dovsienko: most of that is the new driver
<dovsienko>
one has to start somewhere, I guess
<nephele>
dovsienko: yes sure, but i'm going to try and work through this
<nephele>
the less we have to change in wine, the better. less maintance effort on either side
<dovsienko>
other changes arguably could be better with comments as well
<dovsienko>
note that the change to server/signal.c is not conditional on __HAIKU__
<nephele>
Let me know of anything that is upstreamable
<dovsienko>
there's a leftover debug line in server/fd.c
<nephele>
I'm not going to apply the patchset as is dovsienko, so leftover code is OK. Just trying to cut this down one step at a time
<dovsienko>
the change to programs/winedbg/winedbg.c isn't conditional on __HAIKU__ either
<Begasus[m]>
all is installed x512 , still getting the error when running configure, I'll let you guys play with this ;)
<dovsienko>
the "#define HAVE_GETADDRINFO" line in dlls/ws2_32/unixlib.c is not conditional either and points to a problem with the build system, which is supposed to manage that before the .c files get to compile
<dovsienko>
so far my impression is this patch requires more work to be more presentable to the upstream
<nekobot>
[haiku/haiku] 1e4a50ea9249 - RemoteDesktop : improvement on parsing optional ssh port
nephele has quit [Remote host closed the connection]
nephele has joined #haiku
petterhj has quit [Ping timeout: 480 seconds]
<nephele>
x512[m]: in any case your change for dlls/ntdll/unix/serial.c in the wip port is wrong, CS7 and CS8 have to be visible, CS5 and CS6 need to be hidden behind the ifdef
<x512[m]>
Yes I suppose. That patch was made mechanically to fix build error.
<nephele>
that's okay. :) for a proper good port we need to get these things fixed
<Begasus[m]>
x512: where do I find input-event-codes.h? (I see it mentioned in the gtk3 recipe/patchset, but doesn't seem to be included in the package)
<Begasus[m]>
yeah saw that :) guess I can grab it from the work directory
<Begasus[m]>
ok, that worked so far
Begasus_32 has quit [Quit: Vision[]: i've been blurred!]
petterhj has joined #haiku
<Begasus[m]>
dlls/ntdll/unix/file.c:477:(.text+0xc64): undefined reference to `fgetxattr' (lgrep doesn't show me the funtion aside from a few undefined ones)?
<Begasus[m]>
seen this before ... HAVE_SYS_XATTR_H
<Begasus[m]>
one of the things I undef's in the source for 10.6 ...
<Begasus>
nephele, I could (only 2 lines here), but you'll still end up with a link :)
<nephele>
you posted 5 lines, if you use a pastebing, or put those on single lines that is much easier to read than the mess and *HUUGE* link matrix makes out oif it
<nephele>
so from talking it seems that the driver using C++ might be okay, maybe. But no strong opinion yet, but modifying headers to be C++ compatible is not that nice
<Begasus[m]>
x512 https://bpa.st/SGNQ that was how I patched that for the above, using __GNU_SOURCE ... didn't work
<Begasus[m]>
better nephele ? :)
<nephele>
yes
<nephele>
much more readable
<Begasus[m]>
OK, I'll "try" to be aware of it :)
<Begasus[m]>
build succeeded, notepad crashes ;)
<Begasus[m]>
from winecfg: 01b0:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
<nephele>
github no longer renders code diffs for me in webpositive
<nephele>
neochat always opens in lioght mode for me
<Habbie>
The application: ... Debugger --save-report .... has encountered an error
<nephele>
if i go to the appearence tab it suddenly remembers that it's supposed to be in dark mode
<nephele>
Habbie: inception
<Habbie>
yes
<Begasus[m]>
have had that also sometimes nephele
<Habbie>
can somebody try wiggling the top (above RGB) slider in Appearance -> colors around the 127/128 mark a bit? because that crashes Tracker pretty reliably here
<Habbie>
when it goes from light to dark
<Habbie>
or back
<nephele>
no crash for me
<Habbie>
hello KDL
<Begasus[m]>
still on beta here, so can't check that (well, doesn't crash here)
<nephele>
but i am on a slightly olde rhrev
<Habbie>
ok, need to go shopping first
<Begasus[m]>
hrev58808 doesn't crash in qemu
<Habbie>
my KDL crashed
<Habbie>
this is not a very lucky hrev
<Habbie>
this is after d:0:baron crashed in View::ColorUpdated :)
<nephele>
maybe it wasn't a KDL habbie
<Habbie>
'debugger for team 103' oh right
<Habbie>
understood
<nephele>
the debugger can also run in that terminal-like interface if something goes wrong
<Habbie>
yes, makes sense!
<Habbie>
i got 'sc' out of it and now it stopped responding
<nephele>
seems to me you are having fun learning more about the system :)
<Habbie>
yes :)
<Habbie>
some of which i signed up for (stubbornly choosing BIOS over EFI), some of which... less so
<Habbie>
anyway. your color thing is nice, if i ignore the crashes
<Habbie>
is this why we spoke about HSV a few months ago?
<nephele>
that particular patch was written by waddlesplash, but yes, it does use hsl
<Begasus[m]>
habbie: don't use the slider, just click on a darker area :)
<Habbie>
Begasus[m], why?
<Begasus[m]>
still wish Vision could also follow that :)
<nephele>
live color updates are fun
<Begasus[m]>
no crash then habbie ?
<nephele>
Patch Vision? :)
<Habbie>
Begasus[m], no crash? i'm going to use the slider EVEN HARDER
<Begasus[m]>
if only :P
<Begasus[m]>
lol
<Begasus[m]>
patches welcome then :D
<nephele>
Vision can be patches for this if you want
<Habbie>
Begasus[m], in time :)
<nephele>
basically add a checkbox to "use OS color theme" and enable this for new installs (not old)
<nephele>
and when that is set use the OS colors instead of visions own colors
<erysdren>
Vision has always been buggy for me, including bad redraw areas in the lower left (dont have a screenshot right now)
<Begasus>
I remember I had to use an external theme for hexchat on windows to have a dark mode
<erysdren>
not sure if thats a known bug
<Habbie>
i wondered where debugger reports went. after reboot, with no windows on my desktop, i see ;)
<nephele>
my alt key doesn't work in vision reliably recently
<nephele>
I did submit a patch so vision would actually open on screen though
<Begasus>
nephele, did something simular for Vision, changed the colors manually and saved it as a dubplicate in ~/config/settings
<nephele>
erysdren: hmm, never had redraw issues with it
<Begasus>
just had to switch that file with the default one to change colors :)
<nephele>
Begasus: obviously not really the same thing now is it
<nephele>
Vision mostly uses colors that could be OS provided, i think the only different ones are highlight color, and channel ops color
<nephele>
I think Terminal and Vision should get an "follow OS" color scheme to use by default
<Begasus[m]>
never looked at Vision's source nephele , wouldn't know where to start :D
<Begasus[m]>
+1 from me there nephele
<nephele>
excuses ;)
<Begasus[m]>
good thing Terminal can switch color themes
bbjimmy has quit [Quit: Vision[]: i've been blurred!]
<Habbie>
i already made Terminal dark yesterday :)
<Habbie>
ok, now i'm not going to mess with it until this build is -done- ;)
<Begasus[m]>
I've added the QT6.9.0 recipes PR earlier today :P
<Begasus[m]>
kinda "fixed" a bug with clang last week ;)
<Begasus[m]>
and still runs on the updated system?
Guest14842 has left #haiku [#haiku]
Guest14842 has joined #haiku
Guest14842 has left #haiku [#haiku]
HaikuUser has joined #haiku
HaikuUser has quit []
Guest14842 has joined #haiku
<nephele>
Habbie: i just did that :D
<nephele>
Habbie: it complains that it cant find 1 target and cant make 668 ntargets
Guest14842 has left #haiku [#haiku]
mmu_man has joined #haiku
Guest14842 has joined #haiku
dalme has joined #haiku
KapiX has quit [Quit: KapiX]
<Habbie>
nephele, so.. it's not me? i am missing something
<Habbie>
oh crap
<Habbie>
i missed the "can't find 1 target" line
<Habbie>
so @something is required there
<Habbie>
ok, still can't find 1 target
<nephele>
wdym? are you compiling without a target?
<nephele>
it's fine if you want to compile with libbe.so only or something, but if you try to build the hpkg without a @nightly-anyboot you will get a broken image lacking openssl among other things
<Habbie>
trying with @nightly-anyboot now
<Habbie>
@nightly-raw did not work
<nephele>
i doubt that for your issue that this makes a difference, both are supposed to work
<Habbie>
yeah, i thought so
<nephele>
and for building a package they are equivalent
<Habbie>
can't find 1 target, can't make 668 targets
<Habbie>
if only it would tell me which
<nephele>
there is some way to get more verbosity out of jam but i can'
zardshard has left #haiku [Error from remote client]
<nephele>
t recall
zardshard has joined #haiku
<Habbie>
yeah bunch of -d flags
<Habbie>
i'm just surprised this very basic thing is not working for me out of the box :)
<Habbie>
let's try a fresh master just in case
<Habbie>
i also just realised that i've been building anyboot for weeks, only to then immediately use dd to extract the raw out of it ;)
<nephele>
lol
<Habbie>
that dd went straight to the boot medium so it was not an extra dd
<Habbie>
ok. the build on the other machine does not have the "can't find 1 target" notice
Aedil has quit [Quit: Hoch die Republik!]
Aedil has joined #haiku
<Habbie>
PulkoMandy, i think you missed a few Server lines
<PulkoMandy>
There is a "don't know how to make xxx" message at the top
<Habbie>
for libsupc++
<Habbie>
just realised that indeed
<PulkoMandy>
And yes, that's possible, the builder was happy with my changes but it doesn't test all possible profiles, targets, and combinations
<Habbie>
git grep gives me four that you missed, indeed
<Habbie>
my jam reports three
<Begasus>
closing down here, cu peeps!
Begasus has quit [Quit: Vision[]: i've been blurred!]
<Habbie>
hmm. looks like installing gcc_syslibs_devel might have helped
HaikuUser has joined #haiku
<Habbie>
.. do i need buildtools when building haiku on haiku?
<Habbie>
ah. yes.
<Habbie>
is there any situation in which './configure' without args in the haiku tree makes sense?
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
<Habbie>
shouldn't Screenshot be listed in Applications?
Anarchos has joined #haiku
jmairboeck has joined #haiku
fabrirc has joined #haiku
AndrevS has joined #haiku
<Habbie>
timestamps in syslog would be cool
OscarL has joined #haiku
<OscarL>
Habbie: you can enable syslog timestamps.
<Habbie>
oh cool
<OscarL>
just need to uncomment the line "#syslog_time_stamps true" in the kernel setting file
<OscarL>
under /boot/home/config/settings/kernel/drivers
<Habbie>
i see it
<OscarL>
Also... if you are not building the full iso file... you don't really need buildtools.
<Habbie>
any idea why that's off by default?
<OscarL>
slower, and larger log, I guess.
<Habbie>
yeah i suspected that, but building haiku.hpkg also needs buildtools because the loader is in there, is my impression
<OscarL>
you can just "disable" the building of the 32 bits loader.
<Habbie>
ah, i bet i can
<Habbie>
but my 32 bits loader is in fact patched, otherwise it doesn't boot :D
<OscarL>
ah, alright.
<Habbie>
and i missed that part of the build documentation
<Habbie>
and jam is not great at telling me this is why
<OscarL>
in case you need it in the future, you can just comment out line 21 in "haiku/build/jam/packages/Haiku"
<Habbie>
later on i need to test a patch somebody wrote for du
<Habbie>
for that i could skip the loader indeed
<OscarL>
"AddFilesToPackage data platform_loaders : haiku_loader.$(bootTarget) ;"
<Habbie>
good pointer, thanks
<Habbie>
i hope to keep this install around for a while so i shouldn't need it soon
<Habbie>
let's hope i remember on that day :)
<OscarL>
that's what the IRC logs are for :-P
<Habbie>
yeah
<Habbie>
a build failure i had earlier - i found it in old logs!
<Habbie>
but the answer was not mentioned in them ;)
<OscarL>
gcc_syslibs_devel?
<Habbie>
yes
<Habbie>
but it's possible that the actual answer was 'need buildtools'
<Habbie>
not sure
<Habbie>
i can see how buildtools might also provide gcc stuff
<OscarL>
I had that gcc_syslibs_devel related issue once or twice. (around the times the gcc packages get updates, or when trying to build from a different install than the one I usually use).
<OscarL>
best of luck in your efforts.
* OscarL
signs off.
<OscarL>
later folks.
OscarL has quit []
<Anarchos>
is it possible to close the system app_server and use a locally built one ?
<nipos>
The easiest way to do so that I've found so far is building "haiku.hpkg" and rebooting into it.I don't think you can switch the app_server in a running system,but I may be wrong
<nipos>
There's also test_app_server that runs a second app_server within a window,maybe that's enough for what you want to do.
vdamewood has joined #haiku
<Habbie>
oh, i should set up ccache
fabrirc has quit [Quit: Vision[]: i've been blurred!]
<Anarchos>
nipos not sure , as i want to test RemoteDesktop.
<nipos>
No experience with that one,sorry
<Anarchos>
nipos how do you reboot on the local built haiku.hpkg ?
<nipos>
pkgman install /path/to/haiku.hpkg and then reboot
<nipos>
And if something goes wrong,you can always return to the latest working state in the boot loader
Aedil has quit [Ping timeout: 480 seconds]
<Anarchos>
nipos ok nice
<Anarchos>
nipos i can just do 'ham haiku.hpkg' ?
<nipos>
Yes
<Habbie>
you need a target, right? like @nightly-anyboot
<nipos>
No
<nipos>
haiku.hpkg is the target
<Habbie>
ok. i might have confused myself by my build failing for other reasons :)
<jmairboeck>
You probably need the build profile as well, otherwise some parts are missing
<Habbie>
profile, that's the word
<jmairboeck>
notably openssl, so you can't make https connections
<jmairboeck>
which means pkgman won't work because it tries to update the repositories
<nipos>
It does work for local packages however,so you can still reinstall the official haiku.hpkg from a previous state
<nipos>
(That's what I always do,haven't bothered to look for the OpenSSL issue in my test build so far)
<jmairboeck>
and I would add haiku_devel.hpkg as well and install that also, otherwise you can't do any development, and installing the custom one will uninstall the official haiku_devel because of dependencies
<Habbie>
is there a single target that builds all the relevant haiku*.hpkg?
<Habbie>
oh hey haiku_loader is a separate package
<jmairboeck>
there should be a target which builds the Haiku repository, which contains all packages, but I don't know what that is called
<jmairboeck>
haiku_loader is separate because it is uncompressed. The stage 1 loader is too small to handle compression.
<Habbie>
ack
<Habbie>
and the right file not being the first file in the hpkg :)
<nephele>
nipos: wrong. you need the @nightly-anyboot
<nephele>
otherwise it will build something else
<nephele>
openssl is only one issue afaik
<nipos>
I'm pretty sure I don't need it,because I never used it and my install always works just fine,except the SSL issue
<jmairboeck>
I think the default profile is a minimal image, which is useful for bootstrapping but not much else
<nephele>
you may not hit the cases this is at odds with, but it's still wrong advice...
jmairboeck has quit [Quit: Konversation terminated!]
<nipos>
Maybe the default should be changed then.I'd expect the default to produce a fully usable system.
nephele has quit [Quit: Vision[]: i've been blurred!]
nephele has joined #haiku
<nephele>
okay. Your expectation doesn't match here. The advice is still wrong, even if you think it should be different
<nephele>
I don't expect the default to produce a fully usable system fwiw. not even the nightly profile does that, it is missing a lot of software we have on the betas but make little sense in the nightlies
<Habbie>
i noticed!
<nephele>
No WonderBrush? :o
<nephele>
:D
<Habbie>
that i did not notice!
<Habbie>
but i see pkgman has it
<nephele>
WonderBrush v3 would be the shit, would be cool to see it further developed
<nipos>
Nightly is of couse a fully usable system.Isn't all the missing stuff extra packages you can install from pkgman?
<nipos>
Building some broken "minimal" thing by default that everyone tells you not to do because it's broken is really a bad default in my opinion.
<nephele>
it's not "this is bad" it's "this target is for when you know what you are doing"
<nephele>
for example if you need a haiku for self-hosting, testing patches against the system itself but not much else
<nipos>
Isn't Haiku about sane defaults and such?
<nephele>
If you want sane defaults, use the betas
<nipos>
Lol no
<nephele>
the nigthly branch is deliberately unstable, and i think you know that
<nipos>
It's more stable than any Linux I've ever touched,but that's not the point here and I sometimes think you misunderstand what I say on purpose
<nipos>
If you tell people who build their own haiku.hpkg that they should,in most cases,use @nightly-anyboot because the default is missing important stuff,why is @nightly-anyboot not the default?People who really need @minimal could specify that in the command,others would get a usable system with working SSL without having to care about all that.
<nephele>
because you need to use profiles anyway
<nephele>
If you want the default could be error out because you have no build profile
<nephele>
but that just makes it even more annoying if you *really* only want to compile one command or tool unaffected by this
<nephele>
also with the nightly branch beeing unstable I mean that each update might mess up everything. a recent update to the nightlies made keymap settings break. Not that big of a deal, but these random issues crop up on the nightlies
OrangeBomb has quit [Quit: Slacking off]
<nipos>
I still don't see why I need to use profiles or why nightly-anyboot can't be the default,but I also don't think you're going to explain it,so let's just stop wasting our time here.
<nipos>
I know that nightlys can break from time to time.I'm a developer and I know what I'm doing,also that's totally not the point when we're discussing about building own haiku.hpkg
OrangeBomb has joined #haiku
<nephele>
I already explained what I think the reason is, to not have to specify a different target when building components and not the whole package
<nephele>
fwiw there should probably (if there isn't already) be a profile that will build only the relevant packages on it's own and nothing more
<nephele>
in any case, if you disagree feel free to make a review on gerrit, we can see what the rest thinks :)
Nasina has joined #haiku
xet7 has quit [Remote host closed the connection]
xet7 has joined #haiku
AndrevS has quit [Quit: umount /dev/irc]
dpirate has quit [Remote host closed the connection]
dpirate has joined #haiku
neoncortex has quit []
dovsienko has quit [Read error: Connection reset by peer]
<nephele>
why are the deskbar blue folders not translated?
<nephele>
it looks like they should be
dovsienko has joined #haiku
Nasina has quit [Read error: Connection reset by peer]
Anarchos has quit [Quit: Vision[]: i've been blurred!]
Nasina has joined #haiku
Nasina has quit [Remote host closed the connection]
Nasina has joined #haiku
janoz has joined #haiku
<nephele>
waddlesplash: around?
<PulkoMandy>
There is a default profile but it has been broken for a few years. I think most Haiku devs don't really understand hrofiles and what they were supposed to do. We should fix the default profile of course, make it more like nightlies probably?
janus has quit [Ping timeout: 480 seconds]
janoz is now known as janus
<nephele>
hi PulkoMandy. Do you have a second to upstream a patch for me to BeSpider, and then bump the recipe? :)
<PulkoMandy>
No, it's very much past time to sleep now. But you can send me an email and I'll look tomorrow
adrian_ has joined #haiku
AlienSoldier has joined #haiku
xet7 has quit [Remote host closed the connection]
dalme has quit []
B2IA has quit [Quit: Vision[]: i've been blurred!]