We'd need a bit of help from various hardware manufactures too. Yeah, I'm looking at you Broadcom.More driver support
Anyone can help with that. Find some software you like or pick an orphaned port and get hackingMore application support
We'd need a bit of help from various hardware manufactures too. Yeah, I'm looking at you Broadcom.More driver support
Anyone can help with that. Find some software you like or pick an orphaned port and get hackingMore application support
I was thinking the exact thing There is a software "Zekr" (we use in our research) which is present in AUR (Arch User Repository). I will try to port it to FreeBSD, but the question is: Can I port it without having proper programming knowledge? I know about shell scripting, but not familiar much with C, Java etc programming. Maybe I have to look into Porter's Handbook for my answer.Anyone can help with that. Find some software you like or pick an orphaned port and get hacking
This reminded me of Linus Torvalds showing middle finger to NvidiaWe'd need a bit of help from various hardware manufactures too. Yeah, I'm looking at you Broadcom.
Sure. I maintain emulators/fs-uae but I'm not much of a programmer. I can read documentation though, and I know how to build things following the instructions. I do have some C/C++ knowledge, so I do know how to patch the code if necessary. But sometimes I do run into some weird compiler error but then the community is helpful enough to provide pointers that allows me to solve the problem.Can I port it without having proper programming knowledge?
In theory. And yes, very often, this works well, thankfullyFind some software you like or pick an orphaned port and get hacking
Trying the same thing on linux, i tried gentoo, it did not work, there was always a conflict. Meaning here I put option X there I must put option Y and you never get it right. So in some sense freebsd is doing something right what gentoo is doing wrong. But what is it ?
Thanks. I will definitely give it a try. What do you suggest to a beginner porter (like me), to start from Porters Handbook? or some other resource?Sure. I maintain emulators/fs-uae but I'm not much of a programmer. I can read documentation though, and I know how to build things following the instructions. I do have some C/C++ knowledge, so I do know how to patch the code if necessary. But sometimes I do run into some weird compiler error but then the community is helpful enough to provide pointers that allows me to solve the problem.
It just needs someone that's masochistic enough to grind their teeth on it. Speaking of masochistic, I don't know if you've ever create a MS-DOS/Windows batch file? Now that's some seriously convoluted scripting. Been there, done that, never doing that again. But I've seen people do amazing things with it.But I wouldn't touch an electron app, for example. Back when the port of electron itself was still WIP, I found it on github and actually helped a little. That's where I got my opinion that electron is a major PITA and should be banned And then, there's a constantly growing number of projects providing their software in the form of some docker stuff (scripts to create a container? whatever…)
Start there, it has everything important covered. But, if you don't find something you need, have a look in the Mk and Mk/Uses subdirectories of the ports tree. A lot of stuff is documented there in comments.What do you suggest to a beginner porter (like me), to start from Porters Handbook? or some other resource?
Done that, of course. Also done: A little "C standard library" (incomplete, but with curses support) targeting MS-DOS in realmode. And some little tools in C using nothing but the naked win32 API for their GUI. It's horror, but entertaining Sorry for the off-topicSpeaking of masochistic, I don't know if you've ever create a MS-DOS/Windows batch file? Now that's some seriously convoluted scripting.
.bat files are often used to automate a truckload of clicking around. These days, Powershell is supposed to be a modern replacement. My problem with Powershell is not even so much the command syntax or the programming structure, but rather the permissions - if I run it under the wrong 'system account', it doesn't matter if I have admin access on the machine - the script will fail anyway. I like the idea of scripting, but Linux and BSD's do it better than Windows, sorry. Beyond that - it doesn't matter THAT much if you use bash or basic sh.It just needs someone that's masochistic enough to grind their teeth on it. Speaking of masochistic, I don't know if you've ever create a MS-DOS/Windows batch file? Now that's some seriously convoluted scripting. Been there, done that, never doing that again. But I've seen people do amazing things with it.
Although this might be off-topic as well (more addressing "what is wrong with Windows?"), I just have to comment on that:Powershell is supposed to be a modern replacement.
That's RBAC and/or MAC. You can run into the same problems if you enable SELinux on Linux or MAC on FreeBSD. Security is both a boon and a bane.if I run it under the wrong 'system account', it doesn't matter if I have admin access on the machine - the script will fail anyway.
Gawd, you're so old-fashioned! Don you know that ifconfig is known to behave inadequately in modern network environments? All the cool kids are using the "modern" ip tools....It's more that a userland command like ifconfig(8) can actually use the features of drivers...
I worked at a place where our build tool was a massive batch file that would pop off an argument, process it, and then invoke itself again with the shortened arg list. It was not easy to follow....Speaking of masochistic, I don't know if you've ever create a MS-DOS/Windows batch file? Now that's some seriously convoluted scripting. Been there, done that, never doing that again. But I've seen people do amazing things with it.
astyle said:Red Hat is now another piece of commercial software under IBM's control
Arkham Asylum. I know that place.I worked at a place where our build tool was a massive batch file that would pop off an argument, process it, and then invoke itself again with the shortened arg list. It was not easy to follow.
Jose : Are you familiar with concept of recursion ? Sometimes, realizing that kind of thing makes a program easy to follow. As an example, GNU is a recusive acronym that can be expanded infinitely. or the FreeBSD ports tree compilation can be thought of as a directed graph, which makes backtracking and correcting mistakes onI worked at a place where our build tool was a massive batch file that would pop off an argument, process it, and then invoke itself again with the shortened arg list. It was not easy to follow
make config
easier.I agree... it's just that not everybody can easily afford a support contract with IBM. Most of the time, it's really minimal tasks that take 5 minutes to solve with a simple Google query or about an hour to hunt down someone with root permissions.I don't see anything wrong with commercial support contracts.
Everybody must make a living, including RH programmers.
So I guess Arkham still runs Novell these days.Arkham Asylum. I know that place.
I think the Windows batch language of the day didn't have looping constructs.
That's true, but as Tieks points out they are mainly a waste.I don't see anything wrong with commercial support contracts.
Everybody must make a living, including RH programmers.
When I was in college back at turn of the century, one of my Computer Science textbooks mentioned that recursion was simply an easier way to abstractly keep track of actual program execution on hardware. Compiler design was easier when program syntax was recursive.I think the Windows batch language of the day didn't have looping constructs.
I believe most if not all recursive algorithms have an iterative solution that is usually more efficient on real computer hardware because of the overhead of having to keep all the stack frames for the recursive calls. This has led to the invention of "proper tail recursion" which I still struggle to comprehend.
I've never liked the functional stuff. I figured I'm not smart enough to get it. I found out recently that I'm in good company:
Discovering Dennis Ritchie’s Lost Dissertation
Until recently, across a half-century perhaps fewer than a dozen people had ever had the opportunity to read Dennis Ritchie’s dissertation—the intellectual and biographical fork-in-the-road separating an academic career in computer science from the one at Bell Labs leading to C and Unix. Why?computerhistory.org
No, I'm not saying that I'm as smart as Dennis Ritchie.