Hi, Le 2016-09-09 15:12, Andy Mender a écrit : > Greetings, > > Truth be told, I received your e-mail some time after issuing mine. In > fact, together with the digest. > Sorry about that! > > So that we're both on the same page, I will fork your repository (fork > to my GitHub account or simply clone it locally?) > and work with your files not to duplicate things. Then as you > suggested, issue pull requests.
You can do whatever you want. The usual github logic is indeed "forking", working on your fork and making a "pull request". I think this is messy and a terrible usage of git, but that's what github pushes people to do so I will obviously accept this. The simpler way is just a locale clone, then generating forks as patches (use `git format-patch origin/master`, which creates as many well-formatted patches as commits in a single command), which you can simply send us. I will obviously accept this as well. > I understand the thing with tarballs. I know I should not put them to > a git repo and I will not do so from now on. > I figured out a way of building a package for Arch Linux without a > need for the tarball, which I think is much cleaner anyhow. I don't know how Arch Linux packages are done. And I am not telling you necessarily not to have tarballs. I can't say what's best for your use case. I'm just saying that tarballs should not be in the *source* repository. ;-) We can have release tarballs in a download area. And as I was saying, github even automatically generate tarballs when you tag your tree. See mrxvt auto-generated release tarballs: https://github.com/Jehan/mrxvt/releases > I will update the README and include a .desktop file accordingly. It's > fine if both of those are in the build directory, right? Yes, .desktop files are often in root in most projects, though I see we have a share/ directory in mrxvt. In this case, it probably makes more sense to add it under share/. > The .desktop file would be added together with the rest of the files > through "make install". Obviously. You are welcome to update share/Makefile.am for this. > Per my repository, I think I will rename it, restructure it and use it > for hosting PKGBUILDs before they officially go to AUR. Very good idea. > Nothing more. > > I think that's all for now :). Perfect. We've got a plan! :-) Jehan > Best regards, > Andy > > On 9 September 2016 at 14:54, Jehan <je...@zemarmot.net> wrote: > >> Hi Andy, >> >> Le 2016-09-09 14:23, Andy Mender a écrit : >> >>> Hello, >>> >>> I was successful in building an mrxvt package for Arch Linux. If >>> it's >>> OK, >>> I would like to submit it to the Arch User Repository (AUR). To >>> that >>> end I would also like >>> to add a .desktop file to the tarball as many desktops and window >>> managers use them. >> >> Haven't you received my next email where I explained I created a >> proper git repository with the while history from our subversion >> repo (i.e. each SVN commit is now a git commit, and releases are now >> git tags, and the branches are there too)? >> Please make a "fork" of this repository and make pull requests from >> there: https://github.com/Jehan/mrxvt [1] >> >> Yes we would definitely welcome a .desktop file. :-) >> >>> I would then upload the modified tarball to the git repository I >>> created thus far. >> >> I don't understand. Why do you save tarballs in the repository? As >> I said earlier, you should not do this. A source repository is there >> only to save sources. Tarballs should be saved in a download area. >> By the way, github creates tarball automatically for projects from >> tags. So uploading tarball is actually not even necessary at all. >> >>> I also need to know what are the depends and build-depends of >>> mrxvt. I >>> haven't seen >>> >>> this anywhere in the README. Should I assume they're the same as >>> those >>> of rxvt? >> >> You should be able to get the list of dependency by investigating >> the contents of the configure.ac [2]. >> Then we would welcome a pull request to update README with your >> findings. :-) >> >> Of course, I can also do it, but I cannot promise to do it in a >> timely manner. >> >>> Are the above points OK with you? :) >> >> Yes, for .desktop file and README update. But please work from my >> mrxvt git repository for now. >> Thanks! >> >> Jehan >> >> Best regards, >> >> Andy Mender >> >> On 9 September 2016 at 07:02, Andy Mender >> <andymenderu...@gmail.com> >> wrote: >> >> Greetings, >> >> 1. I'm sorry for instantly creating a git repository from all of >> the >> files. I am still new to git >> and I'm not 100% accustomed to creating PKGBUILDs out of git >> repositories. >> >> 2. I have nothing against SourceForge or SVN. I used the latter >> shortly for getting FreeBSD >> kernel source tree snapshots. >> >> 3. I would be very happy if you could help me out with migrating >> the >> project from SVN to git. >>> From the link you attached I read that it's not trivial. >> >> 4. For now, I cleaned up the entire repository and moved both the >> patch file and tarball >> to a separate directory so that I can still build the PKGBUILD for >> Arch Linux. >> >> I'm awaiting your further assistance ;). >> >> Best regards, >> Andy Mender >> >> On 9 September 2016 at 01:12, Jehan <je...@zemarmot.net> wrote: >> Hi Andy, >> >> Le 2016-09-08 23:29, Andy Mender a écrit : >> Thank you kindly for your response. I set myself a git repository >> on >> GitHub at: https://github.com/AndyMender/mrxvt [3] [1] [1] >> >> Please if the goal is actually to take maintainership of the >> project, you should keep its history pristine. So the git commit >> must reflect the SVN commits. Also the SVN branches should be moved >> as git branches. Same for tags. >> See: >> >> > https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git >> [4] >> [2] >> >> If something is not in order, please do let me know. I still have >> much >> >> to learn in terms of GIT usage. Meanwhile, I shall proceed with >> building >> the AUR package(s). >> >> Best regards, >> Andy Mender >> >> On 8 September 2016 at 15:30, <gi1...@gmail.com> wrote: >> >> On Thu, Sep 08, 2016 at 03:13:12PM +0200, Andy Mender wrote: >> >> I am in the process of preparing a PKGBUILD for Arch Linux to add >> mrxvt to AUR. I noticed that active development of this terminal >> emulator has somewhat ceased. Would it be possible for me to join >> development or fork the project to a git repository? I am far >> more >> familiar with git than with SourceForge. >> >> That's Free Software, so there is no need to ask for forking. >> Though >> it's always cool to say it of course. ;-) >> But if you mean rather to do a rebirth of the project (i.e. >> keeping >> the name and simply moving the upstream to a new repository), then >> that's worth discussing. >> I am in favor to say that we should see after a few commits at >> least, >> and then if it looks like you are really giving a second life to >> mrxvt, we should go for it and officially give maintainership. >> >> Dear Andy, >> >> I use mrxvt as my only terminal emulator on about 5 different >> systems >> (all Debian). I've also completely run out of free time, so I >> will >> only >> ever fix bugs that affect me! >> >> I would love it if we moved from SVN to git! Sourceforge has git, >> so we >> needn't move away from SourceForge. But can move if the person >> doing the >> work chooses. > > I would prefer not staying on Sourceforge after the unfortunate > events which happened (even though it changed ownership since then). > Anyway I see that you chose Github above. > >>> If you want admin access so you can udpate the website / tracker >>> let me >>> know. (I think Jehan volunteered to move everything to GitLab >>> sometime ago but he ran out of time as well...). > > Yes I am very sorry for this. I really wanted to keep hacking mrxvt, > and really wanted to finish someday my work rather than keeping this > unfinished feeling. But now I see that I don't think I can make the > time for this anymore. It is not my main priority nowadays. > > So it is better if someone takes the baby from us. > > Since you seem a little unfamiliar with all git arcanes, I can at > least take the time to rewrite the history into a git repository on > github, then you can simply "fork" from it. Would you want this? But > please don't work from a broken history. It just won't do it! > > Also why did you add release tarball and patch files directly into > the tree root? > I see also you have committed a lot of generated files. Do not > commit > generated files (sometimes there are acceptable reasons for some > generated files, but here this is not the case for all the build > files > you added). > > If you could please fix all these issues first? :-) > Thanks. > > Jehan > >>> GI >>> >>> -- >>> <LIFE><!----Insert boring stuff here----></LIFE> >> >> Links: >> ------ >> [1] https://github.com/AndyMender/mrxvt [3] [1] > > ------------------------------------------------------------------------------ > >> _______________________________________________ >> Materm-devel mailing list >> Materm-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/materm-devel [5] [3] >> mrxvt home page: http://materm.sourceforge.net [6] [4] > > -- > Que la Sainte Marmotte soit avec moi! > Pour me contacter: > IM: je...@zemarmot.net > email: je...@zemarmot.net > http://girinstud.io [7] [5] > http://film.zemarmot.net [8] [6] > Patreon: https://patreon.com/zemarmot [9] [7] > Tipeee: https://www.tipeee.com/zemarmot [10] [8] > > Links: > ------ > [1] https://github.com/AndyMender/mrxvt [3] > [2] > https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git > [4] > [3] https://lists.sourceforge.net/lists/listinfo/materm-devel [5] > [4] http://materm.sourceforge.net [6] > [5] http://girinstud.io [7] > [6] http://film.zemarmot.net [8] > [7] https://patreon.com/zemarmot [9] > [8] https://www.tipeee.com/zemarmot [10] > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Materm-devel mailing list > Materm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/materm-devel [5] > mrxvt home page: http://materm.sourceforge.net [6] > > -- > Que la Sainte Marmotte soit avec moi! > Pour me contacter: > IM: je...@zemarmot.net > email: je...@zemarmot.net > http://girinstud.io [7] > http://film.zemarmot.net [8] > Patreon: https://patreon.com/zemarmot [9] > Tipeee: https://www.tipeee.com/zemarmot [10] > > > > Links: > ------ > [1] https://github.com/Jehan/mrxvt > [2] http://configure.ac > [3] https://github.com/AndyMender/mrxvt > [4] > https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git > [5] https://lists.sourceforge.net/lists/listinfo/materm-devel > [6] http://materm.sourceforge.net > [7] http://girinstud.io > [8] http://film.zemarmot.net > [9] https://patreon.com/zemarmot > [10] https://www.tipeee.com/zemarmot > > ------------------------------------------------------------------------------ > > _______________________________________________ > Materm-devel mailing list > Materm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/materm-devel > mrxvt home page: http://materm.sourceforge.net -- Que la Sainte Marmotte soit avec moi! Pour me contacter: IM: je...@zemarmot.net email: je...@zemarmot.net http://girinstud.io http://film.zemarmot.net Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ------------------------------------------------------------------------------ _______________________________________________ Materm-devel mailing list Materm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/materm-devel mrxvt home page: http://materm.sourceforge.net
