Re: [proaudio] media-sound/lmms-9999-r1 installation fix (github pull request)

[ Thread Index | Date Index | More lists.tuxfamily.org/proaudio Archives ]



On October 27, 2016 4:12:09 PM GMT+09:00, "Miroslav Šulc" <fordfrog@xxxxxxxxxx> wrote:
>Dne 27.10.2016 v 00:47 Hector Martin "marcan" napsal(a):
>> gentoo-mirror GitHub repos are automatically generated mirrors with
>> metadata cache generation, for direct Git sync users. In this case it
>> seems it was automatically set up to track SVN (maybe this was done
>> for all official overlays in layman). It is not a master repo and
>> sending pull requests against it is meaningless.
>well, here in gentoo we accept pull requests that are made against main
>tree mirror that is hosted on github so from this point it's not that
>meaningless as it might seem.

As far as I know you accept pull requests against gentoo/gentoo, not gentoo-mirror/gentoo. The latter is just an automated mirror that is maintained by a bot. The equivalent of the former, for proaudio, is the SVN repo (or our GitLab repo if you go with the fork). So a pull request against gentoo-mirror/proaudio is meaningless, because who would respond to it and how would it make its way back to SVN? It's just a repo maintained by a bot.

>> Honestly, though, given the dreadful state of the repo, I'm tempted
>to
>> wipe the slate clean and start with a new repo and just move/fix
>> individual packages, and also perhaps make more of an attempt at just
>> getting packages upstreamed in gentoo-portage rather than maintaining
>> an overlay (this was also the suggestion from a Gentoo developer I
>> spoke to).
>i definitely agree with the attempt to get the packages into the main
>tree.

I think what I might do is create my own overlay (but if someone else is onboard with the idea of a clean start, by all means let me know and we can collaborate), get the packages that I care about / can test in there as a staging ground, making sure they can be built and work as intended and are mergeable against the main repo, and then just progressively break them out and try to upstream them. I did some cleanup on the main proaudio overlay git fork, but I just don't have the time to properly maintain the whole thing and clean up the mess.

>> ...
>m.
>
>>
>>
>>
>> On October 27, 2016 6:23:28 AM GMT+09:00, Ingolf Wagner
>> <palipalo9@xxxxxxxxxxxxxx> wrote:
>>
>>     Well this all gets a bit confusing to me.
>>
>>     We have
>>
>>     * a SVN repo
>>     * a github repo
>>     * a gitlab repo.
>>
>>     I've pushed to the gitlab repo for the last 6 month (or so). But
>I've
>>     also seen some action on the SVN, but I was never aware there is
>a
>>     github repo.
>>     I think we have to do some action now. I would love to bring the
>>     proaudio project to live again,
>>
>>     - update the wiki-page (so people see there is something going
>on).
>>     - get rid of mantis issue system (and replace it with the github
>or
>>     gitlab issue system)
>>     - remove old and broken packages.
>>     - use GIT instead of SVN of course.
>>
>>     I don't know how this all works here (because it is not written
>somewhere),
>>     but I'm willing to spend time on get things done. Is there
>somebody else
>>     who want to push proaudio forward?
>>
>>     For that I need an admin/moderator/editor account for Wikipedia
>thou.
>>
>>
>>     Hope this
>>     thread is not ignored by anybody and makes it possible to
>>     bring proaudio alive again.
>>
>>
>>     On 10/26/2016 07:18 PM, Miroslav Šulc wrote:
>>
>>         hi, some time ago i created pull request at
>>         https://github.com/gentoo-mirror/proaudio/pull/1 (the feature
>>         is supported there so i thought it's monitored and used). the
>>         patch fixes lmms installation. m.
>>
>>
>>
>>
>>
>>
>>
>> -- 
>> Hector Martin "marcan" (marcan@xxxxxxxxx)
>> Public key: https://mrcn.st/pub 

-- 
Hector Martin "marcan" (marcan@xxxxxxxxx)
Public key: https://mrcn.st/pub



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/