Re: Feature request

2017-05-08 Thread rmgls
Hi, Thanks for your advice. I will set a feature request on trac. Rmgls rm...@orange.fr <mailto:rm...@orange.fr> > On 5 May 2017, at 23:06, Mojca Miklavec <mo...@macports.org> wrote: > > On 5 May 2017 at 22:04, rmgls wrote: >> hi all, >> >> ins

Re: Feature request

2017-05-05 Thread Mojca Miklavec
t always know how big they are as they are often compiled from source. In case of binary packages (or if the same kind of package was already compiled on the buildbot, only not distributed) we could do that, yes, but someone still needs to write the code to: - collect the data - show the data. Y

Feature request

2017-05-05 Thread rmgls
hi all, installing a port compute all dependancies, and print: installing ... do you want to continue Y/N? its ok! but what would be useful is to print the required space for all packages: i.e. say latex or texlive ... which are big packages. it semms to be important in some situations:

Re: suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-12 Thread Brandon Allbery
On Fri, Apr 12, 2013 at 1:16 AM, Roger Pack rogerdpa...@gmail.com wrote: Suggestion/feature request: it would be nice to spit out a warning or error message that supplemented this particular error message, for instance warning: Portfile started without a PortSystem declaration for its first

Re: suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-12 Thread Clemens Lang
Hi, On Fri, Apr 12, 2013 at 08:33:37AM -0400, Brandon Allbery wrote: This would be somewhat difficult, as before the PortSystem line all the PortFile is is raw Tcl code. It doesn't know that it should be warning about commands defined by PortSystem. while this is true, we could still define a

Re: suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-12 Thread Ryan Schmidt
On Apr 12, 2013, at 09:44, Clemens Lang wrote: On Fri, Apr 12, 2013 at 08:33:37AM -0400, Brandon Allbery wrote: This would be somewhat difficult, as before the PortSystem line all the PortFile is is raw Tcl code. It doesn't know that it should be warning about commands defined by PortSystem.

Re: suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-12 Thread Ryan Schmidt
On Apr 12, 2013, at 00:16, Roger Pack wrote: Also as a further note, on this page: http://guide.macports.org/ section 5.1 Perhaps it should say PortSystem: The top (non comment) line of every Portfile; instead of the current: PortSystem The top line of every Portfile; (the

suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-11 Thread Roger Pack
failure here--I put it *before* the PortSystem line). Suggestion/feature request: it would be nice to spit out a warning or error message that supplemented this particular error message, for instance warning: Portfile started without a PortSystem declaration for its first line then I would have known

Re: Feature Request: easy app bundle creation

2011-12-01 Thread Ryan Schmidt
Remember to Reply All so the conversation stays on the mailing list. On Nov 30, 2011, at 11:43, Roger Pack wrote: On Tue, Nov 29, 2011 at 8:14 PM, Ryan Schmidt wrote: If any port reasonably supports being launched as an app bundle, the port should install that app bundle. It should not be

Feature Request: easy app bundle creation

2011-11-29 Thread Roger Pack
As an extension of the current mpkg functionality, it would be slick to be able to specify something like $ port appify port_name icon=xxx default_exe=yyy which created a standalone app from local ports: ref: http://stackoverflow.com/a/3251285 the current way seems a bit involved. Thanks. -roger-

Re: Feature Request: easy app bundle creation

2011-11-29 Thread Ryan Schmidt
On Nov 29, 2011, at 20:09, Roger Pack wrote: As an extension of the current mpkg functionality, it would be slick to be able to specify something like $ port appify port_name icon=xxx default_exe=yyy which created a standalone app from local ports: ref: http://stackoverflow.com/a/3251285

feature request: tell us where the pkg is.

2011-11-25 Thread Roger Pack
--- Creating pkg for dos2unix-5.1.1 I was left knowing, comfortingly, that a .pkg file had been created. Feature request: tell us *where* it was created, so we can then get to it. ex: I think this one was here: /Users/rogerdpack/.macports/opt/local/var/macports/build

Re: feature request: tell us where the pkg is.

2011-11-25 Thread Jeremy Lavergne
--- Fetching archive for dos2unix --- Unpacking tbz2 archive for dos2unix 5.1.1_0 --- Creating pkg for dos2unix-5.1.1 I was left knowing, comfortingly, that a .pkg file had been created. Feature request: tell us *where* it was created, so we can then get to it. ex: I think this one was here

Re: feature request: tell us where the pkg is.

2011-11-25 Thread Ryan Schmidt
--- Unpacking tbz2 archive for dos2unix 5.1.1_0 --- Creating pkg for dos2unix-5.1.1 I was left knowing, comfortingly, that a .pkg file had been created. Feature request: tell us *where* it was created, so we can then get to it. ex: I think this one was here: /Users/rogerdpack/.macports/opt/local/var

feature request: show if installed for port search

2011-06-24 Thread Roger Pack
Hello. Currently we have: $ port search dvdnav libdvdnav @4.1.3 (devel, multimedia) DVD navigation library Feature request/suggestion $ port search dvdnav libdvdnav @4.1.3 (devel, multimedia) (installed) DVD navigation library Cheers! -roger

Re: feature request: show if installed for port search

2011-06-24 Thread Brandon Allbery
On Fri, Jun 24, 2011 at 11:56, Roger Pack rogerdpa...@gmail.com wrote: Feature request/suggestion $ port search dvdnav libdvdnav @4.1.3 (devel, multimedia) (installed)    DVD navigation library +1 but I'd just have it do a port installed in that case so I can see the variants, currently

feature request: slightly better 'package not available' message

2011-05-06 Thread Roger Pack
Hello all. I tried this the other day: $ sudo port install ack Error: Port ack not found Obviously, what I meant was $ port install p5-app-ack Perhaps it could be made to output possible matches as rubygems currently does, or, like ubuntu packages known to contain that binary or what not.

Re: feature request: slightly better 'package not available' message

2011-05-06 Thread Arno Hautala
On Fri, May 6, 2011 at 08:28, Roger Pack rogerdpa...@gmail.com wrote: Perhaps it could be made to output possible matches as rubygems currently does, or, like ubuntu packages known to contain that binary or what not. port already has the search command for searching within package names,