From: Ryuichi KAWAMATA <mail@rkmathi.net>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] [GSoC2012] Interested in Tags support for Portage
Date: Wed, 4 Apr 2012 19:16:47 +0900 [thread overview]
Message-ID: <CAF3hW-j15U9q8sVw7fRwFXVSJSycYRj-+qOqE=oTMKESVCSBDA@mail.gmail.com> (raw)
In-Reply-To: <1333484051.27869.30.camel@big_daddy.dol-sen.ca>
Hello!
> The best way to keep portato going is to update it's use of portage.
> One of the best ways to do that is to finish the new public_api and
> change portato to use it. It at the very least needs the current code
> updated to the current portage api.
Is this means bugs.gentoo.org #136932?
I checkout "public_api" branch and merge into "master" branch to try.
> For tags support, there are also 2 indexed search utilities used by
> users, eix and esearch. Also gentoolkit,s equery could also benefit
> from tags support for it's searches. Eix being c++ and both esearch and
> equery being python based.
>
> You should consider those as part of the work for tags support project.
I think public_api will solve this problem.
I thought the schedule the idea, "Tags support for Portage" is;
1. Implement tags support for Portage
2. Implement public_api for portage that cover all
3. Implement eix, esearch and equery that use public_api which has
been implemented in "2."
If all milestones would have been implemented, to use Portage's
function by other tools.
How about this idea?
Please point out :)
Thanks.
2012/4/4 Brian Dolbec <dolsen@gentoo.org>:
> On Tue, 2012-04-03 at 18:27 +0900, Ryuichi KAWAMATA wrote:
>> Hello.
>>
>> > As was noted in the wiki, this idea is too small for a complete project
>> > on it's own. You will need to add more to it in order for it to be
>> > considered.
>> I discussed this in gentoo-soc IRC yesterday.
>> And, I decide to add another idea, "To implement tags support for Portato"
>>
>> I know CUI system is very useful because it can use over ssh, and
>> normally it's lightly.
>> But, if we need a system which has much information, I think GUI
>> system is also good.
>> Therefore, I propose this idea.
>>
>> I heard Portato developers are few too.
>> So, I think this idea can help its developing.
>>
>> My goal in this GSoC idea is that;
>> * To develop tags support for Portage
>> * To develop tags support for Portato
>>
>> If there are some strange points in my plan, would you point it?
>>
>> Thanks!
>>
>>
>> 2012/4/3 Brian Dolbec <dolsen@gentoo.org>:
>> > On Tue, 2012-04-03 at 08:24 +0900, Ryuichi KAWAMATA wrote:
>> >> Hello, everybody!
>> >>
>> >> My name is Ryuichi KAKWAMATA, a Japanese student.
>> >> I'm a sophomore from April.
>> >> (Japanese school starts from April to March. :D)
>> >> I'm interesting in the idea "Tags support for Portage."
>> >>
>> >> I like portage because I think it's the cleverest package management system!!
>> >> So, I use it in OSX as Gentoo Prefix too.
>> >>
>> >> Now, there is a idea to improve so, I want to develop it very much.
>> >> I'm good at Python and C programming and knowledge about operating systems.
>> >>
>> >> I want to learn the OSS community and help it too.
>> >>
>> >> Thanks!
>> >>
>> >
>> > Thank you for your interest.
>> >
>> > As was noted in the wiki, this idea is too small for a complete project
>> > on it's own. You will need to add more to it in order for it to be
>> > considered.
>> >
>> > You might want to consider adding both eix and esearch to your proposal
>> > to add tags support to their fast search db's. I would be your contact
>> > for work done to esearch. Contact the upstream developer to discuss
>> > adding tags support to eix.
>> >
>> > That will still likely not be enough to make it a complete project, so
>> > you will need to come up with some additional work to do. Preferably in
>> > the same realm of work as the above, mostly portage. One idea I have
>> > would be to complete work on the portage public_api that was started but
>> > needs additional work to complete. That idea could fill in the project
>> > timeline. Contact me directly if you wish to discuss it further.
>> > --
>> > Brian Dolbec <dolsen@gentoo.org>
>>
>>
>>
>
> Something else I forgot to mention.
>
> For tags support, there are also 2 indexed search utilities used by
> users, eix and esearch. Also gentoolkit,s equery could also benefit
> from tags support for it's searches. Eix being c++ and both esearch and
> equery being python based.
>
> You should consider those as part of the work for tags support project.
> --
> Brian Dolbec <dolsen@gentoo.org>
--
""" """ """ """ """ """ """ """ """ """ """ """ """ """
川又 龍一
(Ryuichi KAWAMATA)
筑波大学 情報学群 情報科学類
(Univ. Tsukuba, College of Information Science)
TEL : 080-2594-3539
""" """ """ """ """ """ """ """ """ """ """ """ """ """
next prev parent reply other threads:[~2012-04-04 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 23:24 [gentoo-soc] [GSoC2012] Interested in Tags support for Portage Ryuichi KAWAMATA
2012-04-03 0:52 ` Brian Dolbec
2012-04-03 9:27 ` Ryuichi KAWAMATA
2012-04-03 14:25 ` Brian Dolbec
2012-04-03 20:14 ` Brian Dolbec
2012-04-03 23:49 ` [gentoo-soc] Bugfixes Slava Bacherikov
2012-04-04 0:35 ` Brian Dolbec
2012-04-04 10:16 ` Ryuichi KAWAMATA [this message]
2012-04-04 14:26 ` [gentoo-soc] [GSoC2012] Interested in Tags support for Portage Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF3hW-j15U9q8sVw7fRwFXVSJSycYRj-+qOqE=oTMKESVCSBDA@mail.gmail.com' \
--to=mail@rkmathi.net \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox