Update ticket - xrootd
Hi, Could someone please take a look at and commit https://trac.macports.org/ticket/43743 thanks in advance Chris smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: ticket port command?!
Thanks for the links, Bradley. I was thinking that it would probably be nice to have a common set of utilities like there to ease portfile development. What do you guys think? On 19 maggio 2014 at 19:28:27, Bradley Giesbrecht (pixi...@macports.org) wrote: On May 13, 2014, at 12:53 AM, Aljaž Srebrnič wrote: On 13/mag/2014, at 06:10, Ryan Schmidt wrote: On May 11, 2014, at 13:49, mk-macpo...@techno.ms wrote: I've been using a shell function to do this for years. Is it in contrib/? I’d like to take a look at it! This may be the script Ryan uses: http://trac.macports.org/browser/users/ryandesign/scripts/portissues I use this script: http://trac.macports.org/browser/users/pixilla/scripts/mp-trac-tickets-port mp-trac-tickets-port name:^dovecot2 Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev -- Aljaž 'g5pw' Srebrnič Sent with Airmail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
All Trac is up again. Shree On May 20, 2014, at 3:24 AM, Ryan Schmidt ryandes...@macports.org wrote: On May 20, 2014, at 05:19, Peter Danecek peter.dane...@bo.ingv.it wrote: I have problems to contact trac and http://www.downforeveryoneorjustme.com/trac.macports.org indicates that this is not only a local problem. Can someone look into this? I've forwarded your message to admin at macosforge dot org; they're the ones who can address infrastructure issues. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
So it is. Thanks for getting it up again! On Tue, May 20, 2014 at 9:34 AM, Shreeraj Karulkar skarul...@apple.comwrote: All Trac is up again. Shree On May 20, 2014, at 3:24 AM, Ryan Schmidt ryandes...@macports.org wrote: On May 20, 2014, at 05:19, Peter Danecek peter.dane...@bo.ingv.it wrote: I have problems to contact trac and http://www.downforeveryoneorjustme.com/trac.macports.org indicates that this is not only a local problem. Can someone look into this? I've forwarded your message to admin at macosforge dot org; they're the ones who can address infrastructure issues. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
Thanks a lot! ~petr On 20 May 2014, at 15:34, Shreeraj Karulkar skarul...@apple.com wrote: All Trac is up again. Shree On May 20, 2014, at 3:24 AM, Ryan Schmidt ryandes...@macports.org wrote: On May 20, 2014, at 05:19, Peter Danecek peter.dane...@bo.ingv.it wrote: I have problems to contact trac and http://www.downforeveryoneorjustme.com/trac.macports.org indicates that this is not only a local problem. Can someone look into this? I've forwarded your message to admin at macosforge dot org; they're the ones who can address infrastructure issues. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Update ticket - xrootd
Hi Chris, Done in r120250 [1]. Cheers! Frank [1] https://trac.macports.org/changeset/120250 On May 20, 2014, at 1:14 AM, Christopher Jones jon...@hep.phy.cam.ac.uk wrote: Hi, Could someone please take a look at and commit https://trac.macports.org/ticket/43743 thanks in advance Chris___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Update ticket - xrootd
Mucho gracias … On 20 May 2014, at 4:04pm, Frank Schima m...@macports.org wrote: Hi Chris, Done in r120250 [1]. Cheers! Frank [1] https://trac.macports.org/changeset/120250 On May 20, 2014, at 1:14 AM, Christopher Jones jon...@hep.phy.cam.ac.uk wrote: Hi, Could someone please take a look at and commit https://trac.macports.org/ticket/43743 thanks in advance Chris___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] gaurav added
On May 20, 2014, at 11:45, MacPorts nore...@macports.org wrote: Page gaurav was added by gau...@macports.org Content: ---8--8--8--8--8--8--8--8 == Gaurav Bansal == - Nickname: gauravb7090 - Mail: gau...@macports.org - IRC: gauravb7090 on freenode Gaurav Bansal is a Google Sumer of Code 2014 (GSoC 2014) participant from the BITS Pilani, who's currently working on his GSoC 2014 project, [wiki:gaurav#pip2port Read Packages from pip]. You can track the progress of the project [https://trac.macports.org/wiki/SummerOfCode2014#pip2port here] and the project roadmap [https://trac.macports.org/wiki/SummerOfCode2014_pip2port here] == Google Summer of Code 2014 == #GSoC2014 === Read Packages from pip === #pip2port The project idea aims at generating portfiles for python packages in pip that are non- existent in MacPorts. Also, the idea aims to bring uniformity to the present system by automating the process of creating ports to make package names in Macports match with the ones in pip which is presently not applicable for each and every port. This can be summarized as – when a user runs a command such as pip2port package-name it returns the port file for that particular python-package. === Progress === The current progress on Read packages from pip can be found [https://trac.macports.org/wiki/SummerOfCode2014#pip2port here] and the roadmap [https://trac.macports.org/wiki/SummerOfCode2014_pip2port here] When referring to other Trac pages, you should use Trac links; see: https://trac.macports.org/wiki/TracLinks In other words, instead of: [https://trac.macports.org/wiki/SummerOfCode2014#pip2port here] use: [wiki:SummerOfCode2014#pip2port here] ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] SummerOfCode modified
On May 17, 2014, at 06:29, MacPorts nore...@macports.org wrote: Page SummerOfCode was changed by sha...@macports.org Diff URL: https://trac.macports.org/wiki/SummerOfCode?action=diffversion=240 Revision 240 Comment: added list of interactive cases Changes: ---8--8--8--8--8--8--8--8 Index: SummerOfCode = --- SummerOfCode (version: 239) +++ SummerOfCode (version: 240) @@ -251,7 +251,22 @@ Write an interactive command-line tool that can be used instead of the non-interactive port(1). (The existing interactive mode of port(1) is actually just batch mode reading from stdin, and is not really interactive.) Factor out code used by both tools into a shared module. -An interactive tool would ask for user input to resolve many situations that cause port(1) to simply error out. For example, if you try to install a port and one of its dependencies conflicts with something already installed, it could ask if you want to deactivate the installed one and its dependents. +An interactive tool would ask for user input to resolve many situations that cause port(1) to simply error out. +All the suggested interactivity use cases are listed below- +1. If you try to install a port and one of its dependencies conflict with something already installed, it could ask if you want to + deactivate the installed one and its dependents and reactivate them after the build. There are two different types of conflicts in MacPorts: activation-time conflicts, and build-time conflicts. The former is modeled by the conflicts keyword built into MacPorts base. The latter is modeled by the conflicts_build keyword in the conflicts_build 1.0 portgroup. What you're talking about refers only to build-time conflicts, not activation-time conflicts. +2. When trying to install a port but one of the files installed by this port is already present, ask the user whether the file should be + overwritten. We don't want to make it easy for the user to overwrite already-present files, because it's almost always wrong for the user to do this. We currently require the user to try again with the -f flag to indicate that they really want to force the operation. If MacPorts is enhanced to automatically ask the user if they want to do this, it should include a message that the correct answer is usually no. +3. When a user tries to install a port, display a list of ports that will be installed as dependencies and ask for confirmation (unless + there aren't any dependencies to be installed), like apt-get does. This could be a good idea, as long as there's a way to turn this feature off for those who want to script MacPorts non-interactively. +4. Asking for permission in a situation where uninstalling a package will break another package that's still installed and depends on + the to-be-uninstalled package. This is another situation where we currently require the user to use the -f flag to indicate that they really do want to break the port's dependents. +5. When installing a port that requires a dependency to have a certain variant, but this variant is not set. Ask the user if it should + reinstall the dependency with that variant. MacPorts base doesn't have a way to specify a dependency on a variant, but the active_variants 1.1 portgroup has been added for this. Ideally, ports would not depend on variants of other ports. Ideally, any quality of a port that another port would need to depend on would be expressed as a subport, not as a variant. Unfortunately, our ports are not in an ideal state. If MacPorts is enhanced to offer the user the choice to reinstall a dependency with another variant, it must make it clear that this could break any already-installed dependents that relied on the previously-selected variants. +6. When activate is ambiguous, present a list of installed ports for the user to choose from. +7. Ask user before rebuilding in rev-upgrade. +8. When a user uninstalls a port using --follow-dependencies, the list of dependencies will be displayed and the user will be asked for + confirmation. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: ticket port command?!
On May 16, 2014, at 21:28, Bradley Giesbrecht wrote:
On May 13, 2014, at 12:53 AM, Aljaž Srebrnič wrote:
On 13/mag/2014, at 06:10, Ryan Schmidt wrote:
On May 11, 2014, at 13:49, mk-macpo...@techno.ms wrote:
I've been using a shell function to do this for years.
Is it in contrib/? I’d like to take a look at it!
This may be the script Ryan uses:
http://trac.macports.org/browser/users/ryandesign/scripts/portissues
I forgot about that script. I didn't like the way the Trac reports looked. What
I use now is just a shell function which runs:
open https://trac.macports.org/query?status=!closedsummary=~${PORT};
Some day I should break that shell function out into a separate file, clean it
up, and publish it.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
