Difference between revisions of "Development Guide"

From Funtoo
Jump to navigation Jump to search
m (Updated videos from #widget to #ev because #widget used http requests instead of https and were thus blocked by the browser (This request has been blocked; the content must be served over HTTPS.()
Line 50: Line 50:
And after all that, you can view and look at bugs that are in queue, To-do, or testing, which Daniel's videos are very great at explaining. Thanks for helping Funtoo Linux better and better.
And after all that, you can view and look at bugs that are in queue, To-do, or testing, which Daniel's videos are very great at explaining. Thanks for helping Funtoo Linux better and better.


<center>{{#widget:YouTube|id=JCg5DWjy6Ro|width=720}}
<center>
 
{{#ev:youtube|https://youtu.be/JCg5DWjy6Ro|autoresize}}
{{#widget:YouTube|id=tuFE9ZgVOpY|width=720}}
{{#ev:youtube|https://youtu.be/tuFE9ZgVOpY|autoresize}}


[[Category:Development]]
[[Category:Development]]

Revision as of 22:10, January 23, 2019

This page is intended to be a developer guide for Funtoo Linux.

   Note

Please see Local Development Setup for a definitive guide on kit internals and how to set up a local Funtoo Linux development environment.

Reference

Learn About Ebuilds

  • Local_Overlay -- take the crash course of setting up a local overlay, revision bumping a package, testing, and syncing to github.
  • Git_local_overlay -- drobbins' local overlay guide, less of a crash course, better permissions, and better suited for large overlays.
  • Portage Variables -- learn about all those variables inside an ebuild, and in make.conf.
  • Forking An Ebuild -- explains how to take an ebuild from Gentoo and fork it, so you can make local changes.
  • Ebuild Functions -- src_unpack, src_compile -- these are ebuild functions. There are others. See all of them and learn how they work.

Funtoo Internals

Portage

Metro

Working With Git

Also check out:

Learning how to help squash out bugs can be a difficult thing to do, especially since sometimes JIRA looks a little overwhelming and confusing. A thank you to Daniel for making some videos (see below) on explaining this better, but there were a couple things left out. So I will take you through that. (With picture reference).

The first thing you're going to want to do is make an account, which is simple as clicking on the 'Log in' button on the top right, then clicking 'Sign up'.

Signupjira.png

After you've made your account, the best way to watch bugs is to click on the 'Agile' drop-down menu, and choose 'Classic'.

Agileclassic.png

Now, we're going to want to change a couple things even with this. By default, the 'Classic' mode takes you to 'Classic Planning Board', you want to change this to 'Classic Task Board'. This makes things much easier to read. I also recommend going to the Views eyeball icon to the right and selecting the List issue view, and the Compact (Kanban) task board mode. This will give you a top-level overview of all our bugs and their statuses, and JIRA will remember your view preferences the next time you log in.

Classicview.png

After that, we're almost ready to rock and roll. We need to also make sure that you're not set to any version or we'll only see a few bugs. So in case it says '1.1' or '1.0' change it to 'Unscheduled'.

Jiraversion.png

And after all that, you can view and look at bugs that are in queue, To-do, or testing, which Daniel's videos are very great at explaining. Thanks for helping Funtoo Linux better and better.