[gentoo-soc] New gentoo packages -- report #8

[gentoo-soc] New gentoo packages -- report #8

[Slava Bacherikov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all.

My project task is creating new version of packages.gentoo.org site.
You could find it on
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-packages.git;a=summary
or on https://github.com/bacher09/gentoo-packages
If you want to submit feature request you may do this by assign issue on
github to me.

Last week I  extended existing views with javascript. For example
checking arch now done in modal window if client allows this. I've
writed filtering view and allow it use in modal window also. It allows
search packages by repository, herd, category, license, use flag. I've
also add caching for some elements that rarely change (like list of all
categories that used in filtering form). I've also created view for
showing information about repository (stats, repository path, feeds,
owner name etc). I created changelog parser (now it not ideal, i plan
also little extend it) but some packages have bad data in changelog (for
example bad date in cdrtools "*cdrtools-1.11.29 (12 Ayg 2002)" typo
error in Aug). My changelog parser could fix some typos errors like
these that I have shown. But some packages have little different format
of changelog, that also trouble.
I've also made some fixes in design and in code.
 
Plans for the this week:
Highlight changelog, save latest changelog section, add to package some
data from newest ebuild in that package (like homepages, etc)

- -- 
Slava Bacherikov <slava@bacherikov.org.ua>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQBTeGAAoJEGjUsUT09EyzFyYP/RddIpFiWQC+L/dbYLsSJVLg
NDjpuk8WUejAMEAEQ+XTTAY54A9SC+2WPrwxgEakZUfdQzPhc55LasgPb1YRg0xB
unN4DgJRPuNWC1SyuORSMxKiqJtVJZJkQtybTAepZ0Ux342bWFB0KM0ZbLIqwtd1
C+DxzEEA7Xpb5o/LyiiMvKx+4YJvIuiFo/v+ieTE6qT/bYgZ38B1x6F+q0rRU6OA
XRvwOCKUbjqM3HQltj79UNbXfl69RQk+wv/h5dWp5F73XiEZiozpd0zB3aIXyaCT
9QZ6rIZdWUHpRFOheTDU/x1klwcWymgR7gLPfPvJ87B8pCyWK+9+jEvk826TOFLj
980fuKhIRcBZSPEM9brPomdxhL6KjT+eGTleRAuk3kM0RqlUimZFPIUCg0VQuiI5
W8fiqCDavkPXoZrKb0ZlLn0T9KFif33gHIHUJ8bVfuKOLVGfaglKCgzexRaVG25s
JfhSFpHrp226quj7P2BPnhllkB2hu3NgT07xQhtUYjWFrW/r6nnmCH1RNM5frjOU
ND7qXQdp5rvje/I32iB88hjmN089v9EElCMohjS5va38/6Cal2uVk5PG0OeqQMBr
l88mHIYkBIN4d8CW/a5in7Q9OEPi7TLE5hutKJX1P2EM0utWQNLSPi7hrY43vts7
lvXsErXsxYyk4kHYUmwQ
=21Hi
-----END PGP SIGNATURE-----

Re: [gentoo-soc] New gentoo packages -- report #8

[Brian Dolbec]

[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]

On Tue, 2012-07-17 at 12:59 +0300, Slava Bacherikov wrote:
> Hello all.
> 
> My project task is creating new version of packages.gentoo.org site.
> You could find it on
> http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-packages.git;a=summary
> or on https://github.com/bacher09/gentoo-packages
> If you want to submit feature request you may do this by assign issue on
> github to me.
> 

>  I created changelog parser (now it not ideal, i plan
> also little extend it) but some packages have bad data in changelog (for
> example bad date in cdrtools "*cdrtools-1.11.29 (12 Ayg 2002)" typo
> error in Aug).

There are more problems than just a few typo's.  In gentoolkit we've had
to ignore some areas that would otherwise cause problems in equery's
changelog.  Check out what gentoolkit does for those.  You may not need
it, but check.


>  My changelog parser could fix some typos errors like
> these that I have shown. But some packages have little different format
> of changelog, that also trouble.
> I've also made some fixes in design and in code.
>  


> Plans for the this week:
> Highlight changelog, save latest changelog section, add to package some
> data from newest ebuild in that package (like homepages, etc)

Been there done that :)

It is quite simple, have a look at porthole's code.  It should be easy
to adapt to django use with very little changes needed.  You will need
to change it to use django/web colors instead of gtk ones.  Change
porthole's portage_lib calls to your PM backend code.  Change the
gtk.Buffer to an html/xml string.  But the highlighting/parsing code is
there and works.

blog: http://dol-sen.blogspot.ca/2009/12/changelog.html

Code:
http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/views/changelog.py;h=97ed9016e83ca8d11888946346fa4d000e88bb9d;hb=HEAD
http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/views/markup.py;h=4456f25058a6dd2db5a16b571e2f537c6ca553fb;hb=HEAD


Using that code, it should not take very long to convert/implement.
I stopped short of making the email addresses click-able.  They should
use bugzilla rather than email people directly.


If you have more questions, you know where to find me :)
-- 
Brian Dolbec <brian.dolbec@gmail.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-soc] New gentoo packages -- report #8

[Slava Bacherikov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> On Tue, 2012-07-17 at 12:59 +0300, Slava Bacherikov wrote:
>> Hello all.
>>
>> My project task is creating new version of packages.gentoo.org site.
>> You could find it on
>>
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-packages.git;a=summary
>> or on https://github.com/bacher09/gentoo-packages
>> If you want to submit feature request you may do this by assign issue on
>> github to me.
>>
>
>> I created changelog parser (now it not ideal, i plan
>> also little extend it) but some packages have bad data in changelog (for
>> example bad date in cdrtools "*cdrtools-1.11.29 (12 Ayg 2002)" typo
>> error in Aug).
>
> There are more problems than just a few typo's. In gentoolkit we've had
> to ignore some areas that would otherwise cause problems in equery's
> changelog. Check out what gentoolkit does for those. You may not need
> it, but check.
>
>
>> My changelog parser could fix some typos errors like
>> these that I have shown. But some packages have little different format
>> of changelog, that also trouble.
>> I've also made some fixes in design and in code.
>>
>
>
>> Plans for the this week:
>> Highlight changelog, save latest changelog section, add to package some
>> data from newest ebuild in that package (like homepages, etc)
>
> Been there done that :)
>
> It is quite simple, have a look at porthole's code. It should be easy
> to adapt to django use with very little changes needed. You will need
> to change it to use django/web colors instead of gtk ones. Change
> porthole's portage_lib calls to your PM backend code. Change the
> gtk.Buffer to an html/xml string. But the highlighting/parsing code is
> there and works.
>
> blog: http://dol-sen.blogspot.ca/2009/12/changelog.html
>
> Code:
>
http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/views/changelog.py;h=97ed9016e83ca8d11888946346fa4d000e88bb9d;hb=HEAD
>
http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/views/markup.py;h=4456f25058a6dd2db5a16b571e2f537c6ca553fb;hb=HEAD
>
>
> Using that code, it should not take very long to convert/implement.
> I stopped short of making the email addresses click-able. They should
> use bugzilla rather than email people directly.
>
>
> If you have more questions, you know where to find me :)
Dol-sen thanks for helping, I was planning use my parser also like
highlighter(maybe pygments lexer). My parser also ignore some areas but
i have idea how don't do so. (I already check my parser on all portage
tree and overlays)

- -- 
Slava Bacherikov <slava@bacherikov.org.ua>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQBtobAAoJEGjUsUT09Eyz1T0QAIjP6nRy7vut9wPW4Y+FGmh3
p8EqDsJAfkcU9Wog3dXRxEEsalpsyf672/MbAaK0/IM7JYTwyd2Q85DZpmJg2HxI
ss/nDN8p6yICCVGWxSdJRC3hTqmvbPJVIQWJXuhXpmeJDBieFW0t8yszCfxhYzRD
ymAdZHPHHCfON+lycRMqf8Wl7ItGd6Xxm+rd35pNWLhBd3yv43p/izxzCWp+D/xR
MloMTnJbSW5lbPgqO+4+JylYJE8bGGgZIOPs7BHNZtiJQK+Dpl6MQxHc2w9WhTTh
iGjvqeHe/xu/fF36BuxHTnb5j9i7N8EthPEPuUD9FlrT6i0y9/wLlZAfMCuOodHT
gS+LUB6ii7pJusMDnYLG9CemWi4BFL3fafIRhvHEtrgyEuV9QAQMs18/BR8N5qAW
Sm4XlIzDGjaiblMucliNXwWl5cqfAh5PuQeYrCv9chQUHqI8miC9z55HAKulvI5J
5O6Qf0uaMYo+DtmYOznp9ncrfunMpWZ1Ch57me9jjGeyI2bLkcMtMex5rRglD7Yr
DJnOVXBTd6EMadqXx7FSJ1czfIQ/jZl0FZjRyZeFYECtdRN8FK0qF02tf9eAvygJ
4wsaNa4Jcp/mK8MkPXeQnTnwZuB7PnJWlZPcWp0LYwyzsc5HnjBlUB4MgoS95tvp
4MkpMBHQ2j01LKdu9Glg
=iGvF
-----END PGP SIGNATURE-----