public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <brian.dolbec@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] New gentoo packages -- report #8
Date: Tue, 17 Jul 2012 18:11:44 -0700	[thread overview]
Message-ID: <1342573904.28664.13.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <50053786.7010004@bacherikov.org.ua>

[-- 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 --]

  reply	other threads:[~2012-07-18  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  9:59 [gentoo-soc] New gentoo packages -- report #8 Slava Bacherikov
2012-07-18  1:11 ` Brian Dolbec [this message]
2012-07-18 15:45   ` Slava Bacherikov

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=1342573904.28664.13.camel@big_daddy.dol-sen.ca \
    --to=brian.dolbec@gmail.com \
    --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