Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 468602 - net-news/quiterss: add live ebuild
Summary: net-news/quiterss: add live ebuild
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Qt Bug Alias
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-04 18:30 UTC by Nikoli
Modified: 2013-05-08 17:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
live ebuild (quiterss-9999.ebuild,1023 bytes, text/plain)
2013-05-04 18:30 UTC, Nikoli 		Details
live ebuild (quiterss-9999.ebuild,999 bytes, text/plain)
2013-05-04 19:00 UTC, Nikoli 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikoli 2013-05-04 18:30:34 UTC 
Created attachment 347368 [details]
live ebuild

Please commit attached live ebuild.
Comment 1 Nikoli 2013-05-04 19:00:50 UTC 
Created attachment 347370 [details]
live ebuild

default S is fine.
Comment 2 Markos Chandras (RETIRED) gentoo-dev 2013-05-05 12:51:21 UTC 
do we really need it in the main tree?
Comment 3 Nikoli 2013-05-05 14:09:07 UTC 
Upstream hg default branch is stable, live ebuild is useful for testing new features. Also now quiterss uses system sqlite without any patches.
Comment 4 Sergey Popov gentoo-dev 2013-05-06 10:35:10 UTC 
+  06 May 2013; Sergey Popov <pinkbyte@gentoo.org> +quiterss-9999.ebuild:
+  Add live ebuild, wrt bug #468602, thanks to Nikoli <nikoli AT lavabit.com>
Comment 5 Ben de Groot (RETIRED) gentoo-dev 2013-05-07 04:29:30 UTC 
(In reply to comment #2)
> do we really need it in the main tree?

No, of course not. We normally keep live ebuilds in the overlay.
Comment 6 Davide Pesavento (RETIRED) gentoo-dev 2013-05-07 13:27:04 UTC 
(In reply to comment #5)
> (In reply to comment #2)
> > do we really need it in the main tree?
> 
> No, of course not. We normally keep live ebuilds in the overlay.

I'm not against having it in portage, provided that it's mostly stable and Nikoli volunteers to proxy-maintain it.
Comment 7 Nikoli 2013-05-07 14:31:22 UTC 
It is my main feed reader now, upstream is responsive, so adding me to metadata.xml is fine.
Comment 8 Sergey Popov gentoo-dev 2013-05-07 15:55:40 UTC 
+  07 May 2013; Sergey Popov <pinkbyte@gentoo.org> metadata.xml:
+  Reformat metadata, add Nikoli <nikoli AT lavabit.com> as maintainer of live
+  ebuild

done
Comment 9 Ben de Groot (RETIRED) gentoo-dev 2013-05-08 16:40:15 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #2)
> > > do we really need it in the main tree?
> > 
> > No, of course not. We normally keep live ebuilds in the overlay.
> 
> I'm not against having it in portage, provided that it's mostly stable and
> Nikoli volunteers to proxy-maintain it.

It is accepted policy (tho not a strict requirement) in Gentoo to not keep live ebuilds in the portage tree, but to prefer snapshots if necessary. Since we have an overlay that we use for practically all of our live ebuilds, I would strongly suggest we do the same here. But I'll leave it up to the actual maintainers to decide.
Comment 10 Michael Palimaka (kensington) gentoo-dev 2013-05-08 17:44:29 UTC 
(In reply to comment #9)
> It is accepted policy (tho not a strict requirement) in Gentoo to not keep
> live ebuilds in the portage tree, but to prefer snapshots if necessary.
> Since we have an overlay that we use for practically all of our live
> ebuilds, I would strongly suggest we do the same here. But I'll leave it up
> to the actual maintainers to decide.

+1