Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny

[Franz Fellner]

The dlang repository offers a gcc ebuild that adds the patchset to build
the gdc. It's behind a USE-Flag. Still it is exactly the same as
sys-devel/gcc::gentoo besides the additional feature.
But I don't think the dlang repo should mask gcc::gentoo.

2018-03-23 12:18 GMT+02:00 Francesco Riosa :

>
>
> Il 23/03/2018 10:48, Ulrich Mueller ha scritto:
> >> On Thu, 22 Mar 2018, Geaaru  wrote:
> >> for both portage and your fork I think that could be interesting add
> >> an extension to PMS for define inside profiles or targets masking of
> >> packages of a particular repslository. Currently PMS doesn't permit
> >> this but have this feature could be help users to define our
> >> profiles under overlays.
> >> Something like this:
> >> sys-devel/gcc::gentoo
> > Conceptually that makes no sense. sys-devel/gcc is the name of an
> > upstream package, so what does it even mean to mask it in one
> > repository but not in another? If it's the same package, then it
> > should behave in the same way, regardless of the repository its ebuild
> > it hosted in (or the package being installed, in which case it is no
> > longer in an ebuild repository).
> >
> > If it is a different package however, then it should have a different
> > name.
> Sorry to say it bluntly but this make no sense at all, even changing a
> USE flag make the package behave wildly differently.
> Once we agree that an upstream (complex enough) package may have
> different incarnations two ebuilds from different maintainers may please
> differently the user.
> I'm not sure this choice belong to profiles but not because same
> upstream correspond to same files on filesystem.
>
> >
> > Ulrich
>
>
>

Re: [gentoo-dev] RFC: using Ninja in more CMake-based packages

[Franz Fellner]

Michał Górny wrote:
 Dnia 2015-06-08, o godz. 12:46:42
 hasufell hasuf...@gentoo.org napisał(a):
 
  On 06/07/2015 05:08 PM, Michał Górny wrote:
   Hello, developers.
   
  [...]
  
  It's not clear to me how the transition should look like.
  
  Are you suggesting Ninja to be the new default or do you want to switch
  per-packages after having tested them?
  
  If the former, then we need a tinderbox-run.
 
 The latter. We don't have the resources to do the former properly,
 and the number of packages relying on GNU make is too large. Some
 ebuilds will also need more extensive changes.

You have your userbase ;)
In order to reach as many as possible you could create a news item. Or a 
mailing list post. Ask them on planet.gentoo.org ;) Tell them how good ninja
performs :)
Ask them to set the generator to ninja in their make.conf to test if their
packages still compile. They create bugs for failing packages and you can
easily hard code good old emake in the specific packages.
As default there probably should always be emake. IMHO a working build system
always is better than a fast but potentially broken one :)

 
 -- 
 Best regards,
 Michał Górny

RE: [gentoo-dev] Re: bug-wrangling (was: [warning] the bug queue has 111 bugs)

[Franz Fellner]

Ian Stakenvicius wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 On 17/04/15 12:13 PM, Franz Fellner wrote:
  Alex Alexander wrote:
  Our bug queue has 111 bugs!
  
  If you have some spare time, please help assign/sort a few bugs.
  
  To view the bug queue, click here: http://bit.ly/m8PQS5
  
  Thanks!
  
  
  Is there something non-devs could do? Would it be OK to just CC
  HERD mail from epkginfo (as I am not allowed to reassign). Because
  I at least once a day browse the bug database and could at least CC
  some of the new bugs.
  
 
 A few years before I became I dev, I did a short stint as a
 bug-wrangler -- iirc all you need to do is train yourself via the
 bug-wrangling guide and find someone to vouch for you in order to
 obtain write-access to bugzilla.  I don't know who you would talk to
 about this right now (NP-Hardass maybe??) but I'm sure that we could
 use the help, if you wanted to lend a hand.

Ian, thx for your answer!
I thought about it if I really want to become a DEV, and I still don't know.
I think I will just go and contact bug-wranglers and look what's happending ;)

It just hurts to see those daily messages about un-assigned bugs :/

 
 
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2
 
 iF4EAREIAAYFAlUxSJgACgkQ2ugaI38ACPCQJwD9HCxFXXsnUXR5WU3dHBsvO93Z
 v7u2nzotdNAREAOBRekBAKRpu8xdSfxeE5GIBF0KOEGBqNMZ3Mtl2jjluN7EQZfs
 =qR8R
 -END PGP SIGNATURE-
 

RE: [gentoo-dev] [warning] the bug queue has 111 bugs

[Franz Fellner]

Alex Alexander wrote:
 Our bug queue has 111 bugs!
 
 If you have some spare time, please help assign/sort a few bugs.
 
 To view the bug queue, click here: http://bit.ly/m8PQS5
 
 Thanks!
 

Is there something non-devs could do?
Would it be OK to just CC HERD mail from epkginfo (as I am not allowed to 
reassign).
Because I at least once a day browse the bug database and could at least CC 
some of the new bugs.