Re: [gentoo-portage-dev] Helping out
Am 06.01.2014 21:46, schrieb Jesus Rivero (Neurogeek): Hi all, WRT dolsen's email to -dev: ...Those interested in joining, please subscribe to the gentoo-portage-dev list and send an email stating what you can offer and any ideas you have to improve portage's code base. I'd like to help out. I'm somewhat familiar with portage internals and I know Python. Let me know what do you need from me. I tried to compile a list of bugs for people to get started. If you aren't interested in any of those, feel free to roam the bugs assigned to dev-portage. There are more than enough. Bug 490358 - sys-apps/portage: when using git repo directly, version should include git sha1 (edit) Bug 490896 - make.conf `source`: support expanding variables Bug 489088 - sys-apps/portage-2.2.7: FEATURES='cgroup ipc-sandbox network-sandbox' do not fail gracefully Somewhat larger project that needs discussion with the team: Bug 478384 - sys-apps/portage: repos.conf: support tarball (emerge-webrsync) Split this bug in small self contained tasks and file a bug for each task: Bug 480190 - implement GLEP-58 to 61 Cheers, -- Jesus Rivero (Neurogeek) Gentoo Developer
Re: [gentoo-portage-dev] Bugzilla workflow
Here's a new version of the workflow that tries to incorporate all the comments. This should go into the DEVELOPING file once everyone agrees. Bugzilla There always exists a tracker bug, named: [Tracker] sys-apps/portage-next version. This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, until it gets closed when Y changes and a new one is opened. Whenever a commit for a specific bug is made to the git repo, the corresponding bug gets changed in the following ways: * InVCS is added to Keywords * The bug is marked as blocking the tracker for the next version * A comment is added saying: This is fixed in git: url to commit (note that the bug stays open) After a release all open bugs blocking the tracker are closed with the comment This is fixed in version.. For individual open bugs it is encouraged to set UNCONFIRMED, CONFIRMED or IN_PROGESS as appropriate. There are a number of bugs named [TRACKER] * that collect bugs for specific topics. Confirmed bugs should be marked as blocking these tracker bugs if appropriate. It is encouraged to set the alias field for frequently used bugs.
Re: [gentoo-portage-dev] Helping out
2014-01-06 21:46 Jesus Rivero (Neurogeek) napisał(a): Let me know what do you need from me. You can help in porting various functions to not use deprecated objects. Examples: PORTDIR (when used as internal config variable) PORTDIR_OVERLAY (when used as internal config variable) mainRepo (outside pym/portage/repository/config.py) mainRepoLocation (outside pym/portage/repository/config.py) porttree_root -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part.
[gentoo-portage-dev] Re: [gentoo-dev] Portage team, Zac's development break and stepping down as lead
Hi everyone, I saw the email sent to the dev mailing list asking for help on portage. I'm not sure how much interest the post has generated, but if help is still needed, I'd be more than willing to help out. I have good familiarity with bash and python (I use both extensively at work). I'm not too familiar with portage's internals but willing to learn. If help is still needed, is there any documentation for starting development or any good pointers for me to get started? Regards, Pavel
Re: [gentoo-portage-dev] Re: [gentoo-dev] Portage team, Zac's development break and stepping down as lead
On Tue, 2014-01-07 at 16:53 -0800, Pavel Kazakov wrote: Hi everyone, I saw the email sent to the dev mailing list asking for help on portage. I'm not sure how much interest the post has generated, but if help is still needed, I'd be more than willing to help out. I have good familiarity with bash and python (I use both extensively at work). I'm not too familiar with portage's internals but willing to learn. If help is still needed, is there any documentation for starting development or any good pointers for me to get started? Regards, Pavel Welcome. There have been several so far, but, the more the better. It will take the load off any one individual. We all (well, most) have real lives that we also need to attend to. ;) For best the best documentation, enable the epydoc use flag and re-emerge portage. There are several bugs to start working on. Also there are some gleps that need to be attended to. See the email Sebastian has sent out with a number of open bugs. I will be laying out a plan for the sync operations change I am proposing to do. If we can come to an agreement on that, then there will also be that to implement. So for now, join, start delving into the code, see what you can do. Ask questions... We will need to establish some meetings after some newcomers have had a bit of time to see what needs doing. We can start making some decisions then. Thank you. -- Brian Dolbec dol...@gentoo.org signature.asc Description: This is a digitally signed message part
Re: [gentoo-portage-dev] Portage team, Zac's development break and stepping down as lead
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/07/2014 08:02 PM, Brian Dolbec wrote: Welcome. There have been several so far, but, the more the better. It will take the load off any one individual. We all (well, most) have real lives that we also need to attend to. ;) For best the best documentation, enable the epydoc use flag and re-emerge portage. There are several bugs to start working on. Also there are some gleps that need to be attended to. See the email Sebastian has sent out with a number of open bugs. I will be laying out a plan for the sync operations change I am proposing to do. If we can come to an agreement on that, then there will also be that to implement. So for now, join, start delving into the code, see what you can do. Ask questions... We will need to establish some meetings after some newcomers have had a bit of time to see what needs doing. We can start making some decisions then. Thank you. Thanks! I will get myself familiar with the code base and then start hacking on the list of issues Sebastian has sent out. Regards, Pavel -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSzOdSAAoJENb1ecI556su4mwP/A/SlC7hhrroRbPiZ5jsm8YS qSJIY5K+ePRbJ2W+XmjNgEhpUcoFqzbPXYqtoLwE/FWMiYPLmSRDyhP5aNHC4lya B1y/8ulZ+K0qMwAFeXpqy2Rz/AFAP+A0erq+3ScHJTb1ifY9nwwaXXrgvu2q4yJx qrbU4JIul1zcpX/23EQ62/tQGPpFgXHcPLGg29L7CjyHXfylffE1uIsx0a4QSssS ANC6ct9yzIG3bZ4/PT6BfWwVYLHMCjNxHsyljCGTMCBEzCn6jtm3qm8/QO3uxOd7 dFV9uC17HyWt9XNtYupXrO7l6TIsxSNoDJsh0zoCBXQk4lANBQgfjQ6eYRGXBd0R VCDYU1DDWYeMxZzxmk6UU6FOEyN1epobFR6CynJ//v8yUzyyF/98gb4sFoTdIY0o SAQ8WKLbFSlrWkxEx12e+J/TdYhNwfaQLaX0CkwnqB+wYS8DhJ09y9T3T/OMRMxa Gng6M+Fm39ybgDUcMsOb8tBakTAiqM6/4llNLU01ip3TxpI+CZAW6G6uYfr6Chq5 7qkb9VoYREBXgavnT//2YXRgS3CvKe6pLbNJQ08sfiTd2Rq0UFgB9mWaw/0L3idw fZgX0Rt+tnvAj9Mfz8mq6GsmSTmSqfRt3tmrEIT58Rgm38/HXw8sXkZLxoG1RUnB oIOzcFOLB3R+D5wIYJxV =XSuE -END PGP SIGNATURE-
