Re: How to get a full list of dependents?
On 10/02/2013, at 1:11 PM, Ian Wadham wrote: > On 10/02/2013, at 7:37 AM, Joshua Root wrote: >> MacPorts_Framework is still in a pretty "pre-alpha" state, so I wouldn't >> worry too much about maintaining compatibility if not doing so will make >> it better. Just make sure you mention the interface breakage in the >> commit logs, and fix Pallet to match. > > It looks as though backwards compatibility is an impossible ask in an Xcode > environment. For starters, there are all the .xcodeproj files. My Xcode 4.6 > grumbles about them all the time and FAIK has already changed them a lot. > The files in SVN are for Xcode 4.3, I think. > > Then Xcode keeps "pushing" newer features that are somewhat > fundamental, such as automatic reference counting and Interface > Builder layouts with constraints. These are nice features, but not > backwards compatible. > > Re the "pre-alpha" state of Macports_Framework, tell me about it … :-) > > One problem is that there is almost zero error information (in an NSError > object) passed back to Pallet, but lots of "comments to self" in the code > about the need to do something. Another problem is that Pallet ignores > the NSError object anyway and treats all actions as successful. A third > is that actions like "install Growl" should always fail (the Growl port is > broken), but sometimes are said to "succeed" (in the Console messages). > > Macports_Framework has over 12,000 lines of code, and nearly 4,000 > lines are a copy of Apple code for BetterAuthorizationSampleLib, dated > 2007 (Is that code still current, I wonder?). > > Should I persevere with Macports_Framework? It's been a while since I > worked with threads and concurrent processes and Apple's way of doing > things, in Objective C, OS X and Xcode is all new to me. I enjoy a challenge, > but in this case, is it (Macports_Framework) worth the effort? People are > lukewarm about having a GUI for Macports anyway. I am not, but I find > the framework for interacting with Macports to be huge and rather daunting. I have copied this discussion to macports-dev, under a more relevant subject line. Please reply there. Thanks, Ian W. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On 10/02/2013, at 1:57 PM, Lawrence Velázquez wrote: > On Feb 9, 2013, at 9:11 PM, Ian Wadham wrote: >>> This (and other questions regarding development of Pallet and >>> MacPorts.framework) is probably more suited to the macports-dev list, >>> where you'll get the attention of more developer types. >> >> I will, if and when I am ready, but I am still a newcomer in these parts, >> previously (and still) in C++, Qt and KDE. > > Don't feel like macports-dev is only for grizzled veterans or anything. The > difference between macports-users and macports-dev is that of topic, not > experience. I ask n00b development questions on macports-dev all the time. > > Also note that having development-related discussions on macports-users makes > it marginally more difficult to find them in the future. Your points are taken. I will certainly canvas design issues on macports-dev, if I get as far as designing anything … also the odd "how to", if people do not mind. Cheers, Ian W. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On Feb 9, 2013, at 9:11 PM, Ian Wadham wrote: >> This (and other questions regarding development of Pallet and >> MacPorts.framework) is probably more suited to the macports-dev list, >> where you'll get the attention of more developer types. > > I will, if and when I am ready, but I am still a newcomer in these parts, > previously (and still) in C++, Qt and KDE. Don't feel like macports-dev is only for grizzled veterans or anything. The difference between macports-users and macports-dev is that of topic, not experience. I ask n00b development questions on macports-dev all the time. Also note that having development-related discussions on macports-users makes it marginally more difficult to find them in the future. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On 10/02/2013, at 7:37 AM, Joshua Root wrote: >> Apparently commands such as "port dependents xxx" or "port echo >> dependentof:xxx" >> will only list *installed* dependents --- and "xxx" must itself be installed. >> >> How can I get a full list of ports that are dependents of "xxx", whether or >> not >> they or "xxx" are installed? >> >> ATM I would like to see which ports depend on Growl and which depend on >> MacPorts_Framework. Pallet depends on both, but are there others? > > port echo depends:Growl > > This uses the index, so it won't find dependencies that are added in > non-default variants. Thanks, Joshua. I can't see it in "man port", though :-) >> If I wish to make a change in MacPorts_Framework, what might be the impact >> on ports other than Pallet, or is Pallet the only user? >> >> Ditto, if I wish to remove the dependency of Pallet on Growl? Do other ports >> use it successfully? It is apparently not doing anything in Pallet. > > This (and other questions regarding development of Pallet and > MacPorts.framework) is probably more suited to the macports-dev list, > where you'll get the attention of more developer types. I will, if and when I am ready, but I am still a newcomer in these parts, previously (and still) in C++, Qt and KDE. > MacPorts_Framework is still in a pretty "pre-alpha" state, so I wouldn't > worry too much about maintaining compatibility if not doing so will make > it better. Just make sure you mention the interface breakage in the > commit logs, and fix Pallet to match. It looks as though backwards compatibility is an impossible ask in an Xcode environment. For starters, there are all the .xcodeproj files. My Xcode 4.6 grumbles about them all the time and FAIK has already changed them a lot. The files in SVN are for Xcode 4.3, I think. Then Xcode keeps "pushing" newer features that are somewhat fundamental, such as automatic reference counting and Interface Builder layouts with constraints. These are nice features, but not backwards compatible. Re the "pre-alpha" state of Macports_Framework, tell me about it … :-) One problem is that there is almost zero error information (in an NSError object) passed back to Pallet, but lots of "comments to self" in the code about the need to do something. Another problem is that Pallet ignores the NSError object anyway and treats all actions as successful. A third is that actions like "install Growl" should always fail (the Growl port is broken), but sometimes are said to "succeed" (in the Console messages). Macports_Framework has over 12,000 lines of code, and nearly 4,000 lines are a copy of Apple code for BetterAuthorizationSampleLib, dated 2007 (Is that code still current, I wonder?). Should I persevere with Macports_Framework? It's been a while since I worked with threads and concurrent processes and Apple's way of doing things, in Objective C, OS X and Xcode is all new to me. I enjoy a challenge, but in this case, is it (Macports_Framework) worth the effort? People are lukewarm about having a GUI for Macports anyway. I am not, but I find the framework for interacting with Macports to be huge and rather daunting. > Growl support is good to have, but Pallet should still be usable without > Growl. I have commented it out for the moment … ;-) All the best, Ian W. P.S. Sorry about ranting OT ... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
How to get a full list of dependents?
> Apparently commands such as "port dependents xxx" or "port echo > dependentof:xxx" > will only list *installed* dependents --- and "xxx" must itself be installed. > > How can I get a full list of ports that are dependents of "xxx", whether or > not > they or "xxx" are installed? > > ATM I would like to see which ports depend on Growl and which depend on > MacPorts_Framework. Pallet depends on both, but are there others? port echo depends:Growl This uses the index, so it won't find dependencies that are added in non-default variants. > If I wish to make a change in MacPorts_Framework, what might be the impact > on ports other than Pallet, or is Pallet the only user? > > Ditto, if I wish to remove the dependency of Pallet on Growl? Do other ports > use it successfully? It is apparently not doing anything in Pallet. This (and other questions regarding development of Pallet and MacPorts.framework) is probably more suited to the macports-dev list, where you'll get the attention of more developer types. MacPorts_Framework is still in a pretty "pre-alpha" state, so I wouldn't worry too much about maintaining compatibility if not doing so will make it better. Just make sure you mention the interface breakage in the commit logs, and fix Pallet to match. Growl support is good to have, but Pallet should still be usable without Growl. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On Feb 8, 2013, at 17:57, Ian Wadham wrote: > BTW, I was under the impression that Macports works with a SQLite > database. Could I write SQL SELECT commands for that? i.e. read > only access. The SQLite database is the registry, i.e. only the ports that are installed on your system. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On 08/02/2013, at 6:13 PM, Ryan Schmidt wrote: > On Feb 7, 2013, at 23:26, Ian Wadham wrote: >> How can I get a full list of ports that are dependents of "xxx", whether or >> not >> they or "xxx" are installed? > > I grep the Portfiles, which tells me Pallet is the only user of > MacPorts_Framework at this time—at least, the only one for which we have a > port: > > $ port file all | xargs grep :MacPorts_Framework > /Users/rschmidt/macports/dports/sysutils/Pallet/Portfile:depends_lib-append >port:MacPorts_Framework > $ Thanks, Ryan. I get the general idea and can refine it with a script as I go along. BTW, I was under the impression that Macports works with a SQLite database. Could I write SQL SELECT commands for that? i.e. read only access. Cheers, Ian W. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to get a full list of dependents?
On Feb 7, 2013, at 23:26, Ian Wadham wrote: > Apparently commands such as "port dependents xxx" or "port echo > dependentof:xxx" > will only list *installed* dependents --- and "xxx" must itself be installed. > > How can I get a full list of ports that are dependents of "xxx", whether or > not > they or "xxx" are installed? > > ATM I would like to see which ports depend on Growl and which depend on > MacPorts_Framework. Pallet depends on both, but are there others? > > If I wish to make a change in MacPorts_Framework, what might be the impact > on ports other than Pallet, or is Pallet the only user? > > Ditto, if I wish to remove the dependency of Pallet on Growl? Do other ports > use it successfully? It is apparently not doing anything in Pallet. I grep the Portfiles, which tells me Pallet is the only user of MacPorts_Framework at this time—at least, the only one for which we have a port: $ port file all | xargs grep :MacPorts_Framework /Users/rschmidt/macports/dports/sysutils/Pallet/Portfile:depends_lib-append port:MacPorts_Framework $ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
How to get a full list of dependents?
Apparently commands such as "port dependents xxx" or "port echo dependentof:xxx" will only list *installed* dependents --- and "xxx" must itself be installed. How can I get a full list of ports that are dependents of "xxx", whether or not they or "xxx" are installed? ATM I would like to see which ports depend on Growl and which depend on MacPorts_Framework. Pallet depends on both, but are there others? If I wish to make a change in MacPorts_Framework, what might be the impact on ports other than Pallet, or is Pallet the only user? Ditto, if I wish to remove the dependency of Pallet on Growl? Do other ports use it successfully? It is apparently not doing anything in Pallet. All the best, Ian W. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
