[haikuports] Re: development beginner
- From: pulkomandy@xxxxxxxxxxxxx
- To: haikuports@xxxxxxxxxxxxx
- Date: Tue, 17 May 2022 08:12:27 +0000
Hello!
17 mai 2022, 01:29 "Rog Fanther" <haikufanther@xxxxxxxxx> a écrit:
Do you mean fixing the recipes in haikuports ? No problem, but how do I
search for those that use freetype-config ?
If you have a local checkout of haikuports you can use git grep:
cd haikuports
git grep freetype-config
It will give results for things using freetype-config directly in the recipe
(probably not a lot of them). For other software I guess we will only discover
it as we rebuild it.
Now I have to choose and config an IDE ( or not ) and some simple text
editor. Used VIM to test with BePDF, but even if my fingers still remember
the vi keys, I´d prefer something more "notepad-like". IDEs that seem
interesting are Palladin and Ideam, but as both have some issues, maybe one
of them will turn into tool and project at the same time.
Yes, Paladin (combined with either Koder or Pe) is probably the best choice
here, and indeed still very much work-in-progress. Unless you decide to use one
of a few ported applications: it should be possible to use Qt Creator, Monkey
Studio, or Netbeans on Haiku.
However, being myself used to Vim and Terminal as my main development
environment, I can't comment much more on these.
I have looked at haikuporter, when directed at the forum, but from what I
could understand they are tools to create the hpkg´s after the code is
complete and stored somewhere. And to add to the confusion, the site mentions
haikuporter and a "new " haikuporterPM.
Can you link to the page mentionning these? The "new" package-management
enabled Haikuporter has been in use for several years now, so it's time we
delete or reword these pages.
Anyway, yes, that's correct, haikuporter is only to build packages. You got
answers about it because you used the haikuports mailing list. Maybe
https://www.freelists.org/list/haiku-3rdparty-dev is a better place for the ;
questions not related to haikuporter.
I would like just some simple explanation ( as I said, I understand some
questions will seem silly, but the documention in the Haiku sites also need
some fixes and/or organization, due to outdated things ) .
No problem, we are aware that the website is very far from perfect. I am
(slowly) trying to improve some things but currently my efforts are on
documenting the OS internals.
From I understand until now , the workflow would be something like
Fork project at Github -> clone to local machine -> work at project -> create
pull requests
Yes.
Then, if the project is already at haikuports, after the owner of the project
approves the pull requests, it will be recompiled by the haikuports server.
Before the haikuports builder can build it, it needs a "recipe" file updated in
the haikuports repository (github.com/haikuports/haikuports). This lets the
builder know where the sources are and how to build them.
And if the owner of the project ( like BePDF, for example ) isn´t around
anymore ?
You will find out that a lot of the projects for Haiku are hosted at
http://github.com/haikuarchives. This is a collectively owned place, where ;
several of the Haiku contributors and a few other people have access. So there
should always be someone to review and merge your pull requests. If you show
enough interest on a specific app for some time,
we will probably also grant you rights to make commits there directly without
needing someone else to approve them.
Should haikuporter / haikuports be used to download the projects, and that
would also implement fixes that one would need to otherwise discover alone ?
Not really, if you just want to work on a specific app it's probably easier to
work directly in its repository and not worry about the packaging by haikuports
at first. We can see about updating the packages when you have done enough work
on the app to prepare a new release.
--
Adrien / PulkoMandy
Other related posts:
