Re: Documentation overhaul

On 16/10/09, Ken Cunningham wrote: On 2016-10-09, at 6:53 AM, Marcel Bischoff wrote: there appear to be quite specific views on how everthing here needs to be This is true, and it doesn't take long to notice -- but over 20,000 ports hang tight together and almost all of them work all

Documentation overhaul

Hi all. As Ryan has identified that the online documentation needs work, I'm hereby volunteering to give it a go. Since there appear to be quite specific views on how everthing here needs to be, I'm asking in advance: - Is that in everyone's interest? - Is there already someone working on it?

Re: Issues with oudated ports / GitHub

On 16/10/08, Brandon Allbery wrote: On Sat, Oct 8, 2016 at 4:12 PM, Marcel Bischoff <mar...@herrbischoff.com> wrote: I for one don't understand why one would carry around all that baggage anyhow. Why not leave the old Trac as is and start fresh with a simple, reduced issue tracker

Re: Issues with oudated ports / GitHub

On 16/10/08, Chris Jones wrote: On 8 Oct 2016, at 11:29 am, Ryan Schmidt wrote: On Oct 7, 2016, at 2:18 PM, Christopher Jones wrote: On 7 Oct 2016, at 8:12 pm, Ryan Schmidt wrote: On Oct 7, 2016, at 1:40

Re: Issues with oudated ports / GitHub

On 16/10/08, Ryan Schmidt wrote: On Oct 8, 2016, at 8:30 AM, Marcel Bischoff <mar...@herrbischoff.com> wrote: On 16/10/08, Ryan Schmidt wrote: Requests for new ports could still be valid after years. This list could be helpful for newcomers that want to create new ports. Totally

Re: Issues with oudated ports / GitHub

On 16/10/07, Brandon Allbery wrote: On Fri, Oct 7, 2016 at 2:38 PM, Daniel J. Luke wrote: the cool kids also aren't writing 'tcl' these days ... ...but the way they write anything else, they might as well be writing fortran... Let me just chime in here and say that

Re: Working with Git

On 16/10/07, Brandon Allbery wrote: On Fri, Oct 7, 2016 at 12:43 PM, Chris Jones wrote: On 07/10/16 17:39, Craig Treleaven wrote: On Oct 7, 2016, at 12:16 PM, Sterling Smith wrote: On Oct 7, 2016, at 7:20AM, Chris Jones

Re: Issues with oudated ports / GitHub

On 16/10/07, Guido Soranzio wrote: [...] I really hope that the migration of MacPorts to GitHub will trigger a collaboration between the two communities at last. That would be swell, indeed. Although I can't shake the feeling that it could be a clash of cultures. Kind of like old school coders

Re: Issues with oudated ports / GitHub

On 16/10/07, Ken Cunningham wrote: And there are "requests for ports" ( I think this means new requests for ports that don’t presently exist, mostly) that go back 11 years. Port submissions that go back the same length of time. Possibly some kind of massive clean-out of the old, dead,

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: While the latter examples are just minor differences, especially things like ghc, fontforge an pandoc are either completely broken and/or severely outdated. I'm not trying to badmouth anyone or anything, just pointing to the higher (successful) update rate in

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: After all, MacPorts maintainers are just some people devoting their free time to writing Portfiles. Sometimes other stuff in life stops them from responding to tickets or addressing certain issues. This is a given. Open source projects are mostly staffed by

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: It looks like others have already responded to most of your points, but I would just add: On Oct 6, 2016, at 12:12 PM, Marcel Bischoff wrote: But if I still cannot install (for example) pandoc because ghc still requires llwm-3.5 which does not compile

Re: Issues with oudated ports / GitHub

On 16/10/06, Daniel J. Luke wrote: [...] If installing software by hand results in more current and more secure software for my development machine, I don't get the point of using MacPorts in the first place. MacPorts provides a way to save the 'recipe' for installing software (and a handy

Re: Issues with oudated ports / GitHub

On 16/10/06, Rainer Müller wrote: Hello Marcel, On 2016-10-06 19:12, Marcel Bischoff wrote: I was advised that I should ask my questions and raise my issues here. I'm currently considering dropping the use of MacPorts altogether as this projects' track record regarding critical updates

Re: Issues with oudated ports / GitHub

ct 6, 2016 at 12:12 PM, Marcel Bischoff <mar...@herrbischoff.com> wrote: Hi all, I was advised that I should ask my questions and raise my issues here. I'm currently considering dropping the use of MacPorts altogether as this projects' track record regarding critical updates of major software

Issues with oudated ports / GitHub

Hi all, I was advised that I should ask my questions and raise my issues here. I'm currently considering dropping the use of MacPorts altogether as this projects' track record regarding critical updates of major software tools is rather underwhelming. Furthermore, I'm asking myself what use it