[gentoo-dev] mono-env.eclass: set a default SRC_URI
I noticed the following addition to mono-env.eclass would be needed to
let us kill go-mono.eclass (setting now obsolete SRC_URI and build
phases relying on base.eclass)
Patch attached
--- mono-env.eclass~ 2013-05-24 20:44:55.0 +0200
+++ mono-env.eclass 2013-05-24 21:18:01.0 +0200
@@ -9,6 +9,8 @@
# @DESCRIPTION:
# Set environment variables commonly used by dotnet packages.
+SRC_URI="http://download.mono-project.com/sources/${PN}/${P}.tar.bz2";
+
EXPORT_FUNCTIONS pkg_setup
if [[ ! ${_MONO_ENV} ]]; then
Re: [gentoo-dev] mono-env.eclass: new eclass to be used by most of dotnet packages
El dom, 19-05-2013 a las 12:31 +0200, Pacho Ramos escribió: > El dom, 14-04-2013 a las 11:40 +0200, Pacho Ramos escribió: > > Due reasons explained here: > > https://bugs.gentoo.org/show_bug.cgi?id=462052#c1 > > > > We would like to start a process of simplifying dotnet maintained > > eclasses a lot because they are currently really hard to maintain. As a > > start point, we will need a simple eclass simply to export some > > variables needed to build most of dotnet packages. That variables are > > currently being exported by mono.eclass, the idea would be to split the > > "environment exporting" part out of it (and deprecate current > > mono.eclass in the future) > > > > > > Updated eclass taking care of previous suggestions Added
Re: [gentoo-dev] robo-stable bugs, the flipside
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23/05/13 03:29 PM, Rich Freeman wrote: > On Thu, May 23, 2013 at 2:49 PM, Ian Stakenvicius > wrote: >> >> Are the sources for the auto-stable etc. script posted somewhere? >> I don't think i've actually seen a URL at all in this thread (or >> the one from a couple of months ago).. > > By all means publish your script when done. That seems like it > would be useful for many, and certainly there would be no > objections when used by package maintainers. It is just automating > a repetitive task. > > Rich > Certainly! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlGfZVYACgkQ2ugaI38ACPDNRQD+O7f2xequ8KK/MmQXjSJHaQmP FB4IVo6tLzuPEhTFqJ4A+gN2gVRNqpL/g9674Uzsjl+znK4z/SNpavTsjKNFdu/q =E6r8 -END PGP SIGNATURE-
Re: [gentoo-dev] robo-stable bugs, the flipside
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23/05/13 04:14 PM, Markos Chandras wrote: > On 23 May 2013 19:49, Ian Stakenvicius wrote: On > 23/05/13 02:40 PM, Markos Chandras wrote: On 23 May 2013 19:11, Ian Stakenvicius wrote: Here's a new question on the robo-stable front -- I want to file a bug (by hand, probably) on the next stable candidate for my package and have the robo-stable script CC arches and STABLEREQ after 30 days (assuming no other bugs pop up) Is that doable? (for those of us too lazy to put an entry in our calendars :) > I guess you could use pybugz + cron to do what you want. > > Are the sources for the auto-stable etc. script posted somewhere? > I don't think i've actually seen a URL at all in this thread (or > the one from a couple of months ago).. > >> > > I believe the sources are hosted here > > http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary > > Perfect, thanks!! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlGfZQgACgkQ2ugaI38ACPD9/AEAgZe/nARVLScK/7iapVuXmLEb vvqDuP2C4Qld5nMfEp4A/iJT+vvpQb26XGZ3tTvXnc1oM4Y7RJPeniWyQGOcVNeZ =2hK+ -END PGP SIGNATURE-
