attached there is the ebuild for the version 0.7beta3.
Created attachment 145001 [details] kblogger-0.7_beta3.ebuild
Done, thanks for the notice. :) On a sidenote, there's no need to attach an ebuild if the existing ebuild in portage works.
(In reply to comment #2) > On a sidenote, there's no need to attach an ebuild if the existing ebuild in > portage works. sorry, but i do not understand the meaning of your phrase. what is wrong?
(In reply to comment #3) > sorry, but i do not understand the meaning of your phrase. what is wrong? First: Every time you comment on a bug, attach something or change an attribute it shows up as an email in a number of peoples inboxes. Needless doing so is considered bug spam. Second: When there are no relevant internal changes to an ebuild you waste a developers time, because he feels to have to diff the existing ebuild with the one you attached, just to notice what you did. So when you did a worthy change to an ebuild, please attach an unified diff as well as a comment why, if it isn't plainly visible, otherwise just don't.