From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D65F2139694 for ; Tue, 7 Mar 2017 16:27:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 07925E0C31; Tue, 7 Mar 2017 16:27:29 +0000 (UTC) Received: from omr-m015e.mx.aol.com (omr-m015e.mx.aol.com [204.29.186.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D81E8E0C31 for ; Tue, 7 Mar 2017 16:27:28 +0000 (UTC) Received: from mtaout-aac02.mx.aol.com (mtaout-aac02.mx.aol.com [172.27.2.34]) by omr-m015e.mx.aol.com (Outbound Mail Relay) with ESMTP id 0ADED38000B4 for ; Tue, 7 Mar 2017 11:27:28 -0500 (EST) Received: from [192.168.1.52] (0x5b3139322e3136382e312e35325d [71.122.242.106]) by mtaout-aac02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 02D2F38000091; Tue, 7 Mar 2017 11:27:26 -0500 (EST) Subject: Re: [gentoo-proxy-maint] Packages up for grabs To: gentoo-proxy-maint@lists.gentoo.org References: <704f3d1a-c8c2-7a56-c0c7-37d6f68d2fc2@gentoo.org> From: james Message-ID: <7f8a94d7-e39f-52d2-a7af-2504312108c2@verizon.net> Date: Tue, 7 Mar 2017 11:27:26 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Proxy Maintainers X-BeenThere: gentoo-proxy-maint@gentoo.org X-BeenThere: gentoo-proxy-maint@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit x-aol-global-disposition: G x-aol-sid: 3039ac1b022258bedf6e4e56 X-AOL-IP: 71.122.242.106 X-Archives-Salt: e9abd172-b625-432d-b2a5-d3a5ce7469cf X-Archives-Hash: 2d0d7f9551f56be9904ce9aa9444f5bc Hey Gokturk, This is great info; and I'll work on this on the weekend and post back, as I'm backed up a wee bit atm. thx, James On 03/06/17 22:34, Gokturk Yuksek wrote: > james: >>>>> PS, where is the latest draft of the devmanual and related >>>>> documents, related to EAPI-6. >> Between proxy-maint, mentors, gentoostats, GSoC, graduate school and >> real life issues, devmanual doesn't get the attention it deserves >> unfortunately. I'll try to deprioritize proxy-maint and mentors in the >> coming months to pay more attention to the others hopefully. >> >>> No problem. Is there a suggested reading list to get current with >>> proxy-maint, gentoo-github basics and other useful docs for proxy work? >> > There's a Gentoo Github Guide here: > https://wiki.gentoo.org/wiki/Gentoo_Github > > Let's try to be more goal oriented here and try to establish a > development environment first. If you want to learn how to utilize > Github for pull requests: > > - Login to your account, browse to 'https://github.com/gentoo/gentoo' > and click the 'Fork' button on the upper right > - If you haven't added your SSH key to Github, do so before proceeding: > https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/ > - Clicking the fork button should redirect you to the page of your fork > of the repository. Click the 'Clone or download' on the screen, copy the > URI (should look something like 'git@github.com:gktrk/gentoo.git'). > - Clone your fork to an appropriate directory in the local machine (I > use "~/stuff/gentoo") by typing 'git clone ' where is > the URI you obtained from the previous step and is the destination > directory. For example "git clone git@github.com:gktrk/gentoo.git > ~/stuff/gentoo". > > Looks like radeontop has a new release (v1.0) according to: > https://github.com/clbr/radeontop/releases. Now let's do a dummy > practice with this fresh dev environment: > > - make sure you have app-portage/repoman installed > - cd into the radeontop package directory in the repo: > $ cd ~/stuff/gentoo/x11-apps/radeontop > - For simplicity, copy the 0.9 ebuild as 1.0: > $ cp radeontop-0.9.ebuild radeontop-1.0.ebuild > It needs more work but we're going to ignore that for now > - Regenerate the manifest: > $ repoman manifest > It will download the tarball for the version 1.0 and record its checksum > - Let's do a bare-bone QA check: > $ repoman full > Uh-oh, it spits 6 'dependency.missingslot' and 1 'ebuild.notadded' > warnings for me. Let's worry about fixing them later. > - Now let's do a runtest, it'd be nice to know if this thing works out > of the box: > $ ebuild radeontop-1.0.ebuild install > This command will go through all the ebuild phases up until > src_install() in the correct order: pkg_pretend() -> pkg_setup() -> > src_unpack() -> src_prepare() -> src_configure() -> src_compile() -> > src_test() -> src_install(). > - Let's eyeball the installation image: > $ find /var/tmp/portage/x11-apps/radeontop-1.0/image/ > I see 'radeontop' under sbin, there's a so-file in lib etc. > - It compiles fine for me, let's perform a clean: > $ ebuild radeontop-1.0.ebuild clean > It will remove all the stuff under '/var/tmp/portage/x11-apps/radeontop' > - Let's commit this. There are two ways to go about it. We prefer the > following: > $ git add radeontop-1.0.ebuild > $ repoman commit > If you don't have a PGP key set, repoman will refuse to commit. If you > don't know how to set it up, you can commit the following way: > $ git add radeontop-1.0.ebuild Manifest > $ git commit > Either way, it will pop-up an editor for you. Make sure the first line > looks like the following: > x11-apps/radeontop: bump to 1.0 -- DO NOT MERGE, TEST PURPOSES ONLY > - Let's push our changes on our fork back to github: > $ git push > - We're done with the command line, browse to the page of our fork on > github. You should be able to see your commit on that page. Click > 'Compare' that is under the green 'Clone or download' button. > - Now you are looking at the total changes you've made. Click the green > 'Create pull request' button on the screen. > - This will create you a template for the pull request and fill in the > title for you. In the body where it says 'Leave a comment', type the > following: > Not ready for merge yet. Pinging @gktrk. > - Click the button 'Create pull request'. > > Once you get to this stage, I'll help you out with the rest. This setup > is far from being optimal and we will need to change many other things > in the future. For now, it should give you some of the basics. > > -- > gokturk >