<jmairboeck>
I did it! I finally got a (somewhat working) texlive 2021 package out of haikuporter! I just created a pull request: https://github.com/haikuports/haikuports/pull/5963 The package and recipe both still need some cleanup and fixes though, I suppose
blu256 has quit [Ping timeout: 480 seconds]
<extrowerk>
jmairboeck: how big is the resulting package?
<extrowerk>
the 132mb texlive is manageable, but the others are still too big. is there any simple way to split them up?
<extrowerk>
the doc package is pretty heavy.
<extrowerk>
jmairboeck: do one have to install the _texmf and the _texmf_doc packages or are they optional? Can texlive work without them?
<jmairboeck>
texlive defines multiple "collections" of packages, about 40 of them, which most Linux distros use for splitting the package, but I don't really know how do that in a managable way
<jmairboeck>
_texmf is required, the doc package is not
<jmairboeck>
in fact, the 2014 didn't even include the docs because the package would get too big
johndrin1water has quit [Ping timeout: 480 seconds]
<jmairboeck>
ah, I haven't noticed that one before, extrowerk
<extrowerk>
i don't think there is anything useful in it.
<extrowerk>
You could remowe the # ADDITIONAL_FILES="tlutils.pm.patch" part if it is not used anymore.
<jmairboeck>
I see it is quite similar to the existing 2014 package with the svn checkout part and such. I have cleaned that up and use the tarballs instead. But I'm not sure if it works correctly. The installer shows some errors because the tlpostcode scripts are missing, but I don't know how to geht them.
<jmairboeck>
yes, as I said, the recipe needs still some cleanup
<extrowerk>
i wrote some comments, but let's see whats Bega thinks about it.
freakazoid333 has quit [Read error: Connection reset by peer]
BrunoSpr has quit [Remote host closed the connection]
nephele[x] has left #haiku [#haiku]
tqh has quit [Quit: Leaving]
blu256 has joined #haiku
Anarchos has joined #haiku
<Anarchos>
congrats PulkoMandy for the report !!!!
<Anarchos>
Progress seem impressive those days
bitigchi has joined #haiku
<nephele[m]>
Lol, I didn't expect to read comments on phoronix commenting on a patch I made
mbrumbelow has joined #haiku
jessicalt has quit [Quit: Vision[0.10.3]: i've been blurred!]
<PulkoMandy>
you're famous now :D
<nephele[m]>
I doubt it :p
bitigchi has quit [Ping timeout: 480 seconds]
junaidnaseer has joined #haiku
<Anarchos>
PulkoMandy what can i do to help you investigate why my touchscreen is not recognized by the hid driver ?
<PulkoMandy>
did you make a bug report with the logs, the HID files, and the things we already discussed?
<PulkoMandy>
having all this information in one place already helps a lot
<Anarchos>
PulkoMandy no cause i want to solve it myself and make a patch instead of a bug report :)
<PulkoMandy>
you should still make a bug report to track what you are doing, it's easier for othr people to help you with debugging
<Anarchos>
PulkoMandy ok. so how to get hte hid files ?
<PulkoMandy>
they are in /tmp when you connect the device
<PulkoMandy>
we already looked into this, decoded them to see what's inside and saw that the device exposes multiple interfaces (one looking like a mouse, one looking more like a tablet, and some vendor specific extra things)
<Anarchos>
ah ok, this one : usb_hid_report_descriptor_22b9_0006_0.bin
<Anarchos>
PulkoMandy what was the command again to dump the hex codes from the bin file ?
<PulkoMandy>
xxd
<PulkoMandy>
xxd -g1 -i fichier.bin
<Anarchos>
ok, i will do the ticket later. Anyway i also try to port the linux driver (to loearn more about drivers on haku)
<PulkoMandy>
I don't know anything about Linux drivers except they always look more complicated and badly commented
<Anarchos>
yes
<Anarchos>
spaghetti pointer mess...
<Anarchos>
i miss the era when every developer put a one liner at top of each code file to describe the file....
gouchi has quit [Remote host closed the connection]
junaidnaseer has quit [Remote host closed the connection]
Kokito has quit [Quit: Vision[0.10.3]: i've been blurred!]
bitigchi has quit [Ping timeout: 480 seconds]
bbjimmy has quit [Quit: Vision[0.10.3]: i've been blurred!]
gouchi has joined #haiku
bbjimmy has joined #haiku
<js>
I created a Matrix Space for Haiku FWIW: #haiku-space:nil.im
tqh has joined #haiku
js has quit [Quit: authenticating]
js has joined #haiku
blu256 has quit [Remote host closed the connection]
blu256 has joined #haiku
<truck>
is there a matrix client for Haiku?
<extrowerk>
truck. there is.
<extrowerk>
but do your own research: https://depot.haiku-os.org/#!/?bcguid=bc1-LSHD&repos=haikuports&arch=x86_64&viewcrttyp=FEATURED&srchexpr=matrix
AlwaysLivid has joined #haiku
<AlwaysLivid>
js, it could be a good idea to differentiate between the matrix space and the official chatroom in ways that are visually clear other than the link?
<AlwaysLivid>
i specifically refrained from creating a space myself btw, because you basically aren't allowed to add existing rooms yet :/
<AlwaysLivid>
as in like, we have a lot of local channels and some channels with different topics e.g. #haiku-3rdparty
<AlwaysLivid>
and we'd have to self-host our own bridges and get rid of the old rooms to do this right
<AlwaysLivid>
eeeeeeeeeeeeeeeek, hope they fix that at some point
bitigchi has joined #haiku
odnes has quit [Remote host closed the connection]
odnes has joined #haiku
<truck>
extrowerk: I see nothing on that page about a client for Haiku. I see a QT5 thing, and that is one of the worst programs I have ever seen. It certainly doesn't act like a BeOs program.
<truck>
but - I'm not really interested in Matrix, and that will continue so long as there is no Haiku program.
<PulkoMandy>
that's your best choice for accessing Matrix from Haiku currently. But not using Matrix is also a valid choice of course :)
Begasus has joined #haiku
Begasus_32 has joined #haiku
<truck>
When/If we get one, I'll look at it again (:
<Begasus>
afk ... looking into the build for texlive :)
<jmairboeck>
Begasus: be warned, this is going to take a few hours, or everything together maybe a day or so
<Begasus>
Hi jmairboeck , thanks for looking into this! I know about the build, expecting (if things go well) a package tomorrow ;)
<jmairboeck>
according to the timestamps, building the source package alone took about 4 hours on my (old and slow) system
<Begasus>
building in VirtualBox (stable), so not as fast, but I managed to get the previous one build :)
<jmairboeck>
I'm curious if this works on 32 bit (can't test that myself, my 32 bit VM is not big enough)
<Begasus>
Running 32bit here, so I'll report back on that
<Not-5835>
[haikuports/haikuports] korli pushed 1 commit to master [+2/-2/±0] https://git.io/JZvik
<jmairboeck>
is the $commandBinDir stuff really needed? I have taken the --bindir stuff from the old recipe, I suppose this would work just fine as well
<Begasus>
Maybe extrowerk can comment on this one also, maybe not realy needed as the line you provided is ok, but at some point we started using
<Begasus>
$commandBinDir* for 32bit
<jmairboeck>
and if I see it correctly, $commandSuffix ends up empty in all cases anyway
<Begasus>
with the mention from extrowerk (see some examples at haikuports) it is the same as "$prefix/bin" for secondary architecture ($binDir reverts to $prefix/bin/x86)
<jmairboeck>
yes, I know that, but for everything else, $binDir is $prefix/bin, if I'm not mistaken (as long as we don't have other secondary architectures)
<Begasus>
maybe it would be good to add "DISABLE_SOURCE_PACKAGE" also
<jmairboeck>
so directly using $prefix/bin should just work the same
<Begasus>
Right on that
<jmairboeck>
isn't DISABLE_SOURCE_PACKAGE only used for repacking binaries?
<jmairboeck>
according to that, for GPL packages, we can't use that. I'm not sure if this is correct here for texlive, but it is declared as GPL v2
<jmairboeck>
for GPL compliance we need to distribute the sources (or at least make them available)
<Begasus>
I think (correct me if I'm wrong) this counts for packages distributed in the official release?
<AlwaysLivid>
If I were to chime in, the best way to achieve GPL compliance with a minimum amount of effort in the longer run would probably be attempting to upstream patches. I'm currently in the process of writing a port for DDrace Network though.
<Begasus>
err ... maybe not
<Begasus>
Also I think the reason Texlive wasn't merged as it was is due to it's size
<Begasus>
The previous version was about 2Gb alone for the package, not counting the source package
<jmairboeck>
yes, I think the best would be to declare the architectures with ? so that it is not built automatically (I think texlive 2014 is not available in the Depot but also needs to be built separately)
<Begasus>
New PR by jmairboeck AlwaysLivid ;)
<AlwaysLivid>
sweet jesus
<jmairboeck>
yes, but it contains a very similar patchset based on the old one
<Begasus>
I shared a link to the download for 32bit and 64bit a while back, that has been shared by someone at the forum
<AlwaysLivid>
It doesn't seem considerably large to me to the point where it would seem disruptive to the developers of the project?
<AlwaysLivid>
Eh, whatever, should keep out of this.
<AlwaysLivid>
but wow TEXLIVE 2021!
<Begasus>
;)
<jmairboeck>
the _texmf subpackage has 1.6 GiB here :)
<jmairboeck>
the doc package 2.4 GiB, the source package is 4.1 GiB
<js>
AlwaysLivid: Sure you can add existing rooms and it's what I did 😉. And it contains the existing IRC rooms and the Matrix-only room.
<AlwaysLivid>
Wait, you can?!
<Begasus>
There have been some talks about splitting up the package, I know some other OS's do it also, but never got around to do that :)
<AlwaysLivid>
I think that as far as license compliance is concerned, you'd also have to think about retaining attribution. As in, adding all previous authors as co-authors to the commit or otherwise listing them. (Since copyright assignment is not an issue, etc.)
<Begasus>
jmairboeck, I think it will take up to 3 days here then to complete ;)
<jmairboeck>
yes, someone should try to split it up further, but I'm not sure whether I am skilled enough to do that, or have time for that
<Begasus>
same here, not enough hours in the day :)
<jmairboeck>
openSUSE for example generates RPM spec files out of the tlpdb using custom scripts, and that results in over 4000 individual packages
<Begasus>
Went through repology looking at how others do it ... lacks time :/
<bitigchi>
what's the issue with underlined menu bar letter shortcuts appearing only in certain locales
<jmairboeck>
I think best would be to split it along the "collections" (there are about 40 of them). I think Debian does that, but I have no idea how to do that using haikuporter
<bitigchi>
is/was there a setting for that
<Begasus>
recording to repology Debian is still at version 2020*
<jmairboeck>
the 2021 was released on the 1st April this year
cocobean has joined #haiku
<julicenri>
Noticed on the press release draft that the release date is listed as June XX, 2021.
<julicenri>
Is June really the ETA month for beta 3?
<AlwaysLivid>
I think we got a two-month heads-up before the beta2 release... but the goal is to make releases more often.
<AlwaysLivid>
I'd guess that it seems like this is the case unless if an unexpected hiccup occurs. The deadline for the translations the last time around was 2 weeks.
<js>
<AlwaysLivid "Wait, you can?!"> Yes. Join #haiku-space:nil.im
<AlwaysLivid>
Already done.
<js>
🙂
<js>
Unfortunately it doesn't show rooms you haven't joined yet, though. Which is why for NetBSD I did this: https://wiki.netbsd.org/wiki/matrix
<js>
* Unfortunately it doesn't show rooms you haven't joined yet, though. Which is why for NetBSD I did this: https://wiki.netbsd.org/matrix
<jmairboeck>
Begasus: I have no idea how the debian package build system works, unfortunately. I have a little experience with the openSUSE build service and took a look at how texlive is built there, but didn't really understand that either. The easiest I found is from Linux From Scratch, which I used as a reference in addition to the existing 2014 package.
Anarchos has quit [Quit: Vision[0.10.3]: i've been blurred!]
<AlwaysLivid>
Changed some metadata in the official Haiku channels so that they stick out a bit more, especially because of the fact that there's probably going to be an increased amount of confusion over the fact that discussion rooms are now popping out in different places.
cocobean has quit [Quit: Page closed]
<AlwaysLivid>
I'm now using the format "Haiku · [general description]"
<js>
how about calling them "Haiku", "Haiku (IRC)" etc.?
<AlwaysLivid>
I thought of using "IRC", but it seems a bit weird, since the official channels look completely ordinary when browsing the server list in e.g. Matrix. Same in XMPP. The integration is pretty good and that, sort of, breaks the immersion.
<js>
also, I wonder if haikuports should have a room 🤔
<AlwaysLivid>
The chats are official too.
<js>
<AlwaysLivid "I thought of using "IRC", but it"> Well, IMO rooms that are bridged to IRC are automatically downgraded to the tiny feature set of IRC
<js>
like, I used a reply just now and I am sure someone on IRC will yell at me any moment now for using a feaeture that is not natively in IRC 😉
<AlwaysLivid>
... Well, that's because the replies pretty much suck on IRC.
<AlwaysLivid>
It's on my TO-DO list to open a pull request and improve that a bit
<AlwaysLivid>
But yeah, if it were up to me, it would be better if discussion rooms that are not localized are somehow made to be obvious as not being associated with the project (e.g. "Haiku Community" on Discord), or further clarify that a channel must not simply be named "Haiku" or something.
<Begasus>
jmairboeck, will do a check on 32bit here, will report back on you later if issues arize :)
<AlwaysLivid>
I'm in 5 Haiku channels and that's causing some sort of degree of confusion to me. Spaces are way too immature for them to e.g. replace the current channels, I think, and they aren't widely adopted across the entire Matrix ecosystem.
<AlwaysLivid>
I'd definitely be interested in the prospect of eventually replacing #haiku:matrix.org with a Space, so that it's like Discord, but open-source, but that will definitely need some time and more in-depth conversations.
<js>
<AlwaysLivid "It's on my TO-DO list to open a "> I did. That backfired at lot. Several hardcore IRC fans chimed in that replies should just be removed from the bridge altogether. I quickly closed the PR.
<js>
<AlwaysLivid "I'd definitely be interested in "> Yeah, once spaces are out of beta, but not before 😉. I switched #netbsd:nil.im back to be the main room instead of the space, and created #netbsd-space:nil.im instead.
<AlwaysLivid>
... so you effectively got bullied into sabotaging your own change due to destructive criticism?
<js>
Ideally, we'd also have haiku-os.org as a matrix server, so it could just be #space:haiku-os.org, #irc:haiku-os.org, etc.
<js>
AlwaysLivid: pretty much, yeah
<AlwaysLivid>
that definitely sounds healthy for everyone involved
<AlwaysLivid>
the feature that was suggested in the first place by the collaborator was the route i considered taking despite the fact that i can't do node lol
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
<js>
who do you mean by the collaborator?
<js>
I think the only real hope is that IRCv3 introduces replies… I think it does but nobody implements it yet
<AlwaysLivid>
lol that's gonna be fun
<js>
IRC will always drag down all other protocols to its own featurelessness when there's a bridge, so the only way forward is to add those features to IRC
<AlwaysLivid>
but then you'd relocate the exact same problem to a much more conservative environment
<js>
which is also why many projects prefer to have the IRC as a separate room for those who want to be stuck with the feature set of the 80s 😉
<jadedctrl>
i'm planning on putting a couple images in a blog post
<jadedctrl>
should they go in static/files/images/, or somewhere else? `o`
AlaskanEmily has joined #haiku
Anarchos has quit [Quit: Vision[0.10.3]: i've been blurred!]
countryboy has joined #haiku
<countryboy>
hello
<nephele[m]>
is trac down?
<mbrumbelow>
nephele[m]: its up for me.
countryboy has left #haiku [#haiku]
B2IA has joined #haiku
<nephele[m]>
i can use it now indeed
<mbrumbelow>
I can almost do everything on Haiku that I can do on Linux. Plenty of bugs but still... with the exception of printing and using Wi-Fi 6, it seems to coming along.
<Begasus>
g'night peeps
Begasus has quit [Quit: Ex-Chat]
junaidnaseer has joined #haiku
<nephele[m]>
printing works for me atleast mostly, not sure why we wouldnt do wifi6 (though its a bit hard to keep travk of what the marketing name refers to exactly for me)
<js>
WiFi 6 is AX
<js>
it mostly won't work because lack of drivers
<js>
and probably because the 802.11 subsystem doesn't support it either
<mbrumbelow>
js: I wrote up a bug recently on Wi-Fi 6 concerning Intel's new card. OpenBSD has the driver working but FreeBSD does not have that driver working just yet.
<js>
mbrumbelow: I think they have the driver working, yes, but not 802.11ax working
<js>
I understood you as you want 802.11ax, not just a driver for a WiFi 6 card to then run it at an older 802.11 version
<mbrumbelow>
That is correct yes
<js>
802.11ax is AFAIK unsupported on anything but Linux ATM
<js>
802.11ax cards in 802.11ac/802.11n mode OTOH is a thing on the BSDs 🙂
<mbrumbelow>
Right
<mbrumbelow>
I doubt we will have it for Beta 3
<nephele[m]>
js: oh, i thought freebsd did ax already, good to know
<js>
nephele: It might be that I'm not up-to-date
<nephele[m]>
as for printing, if you know the gutenprint driver and the url the printer is reachable at it may work, we dont have any fancy autodiscovers though :/
<nephele[m]>
js: i dunno, havent investigated that much so probably just mixed something up :)