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,
>> 
>> 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:
> 
> Yes, it would be nice, but we don'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.
> 
> You may open a feature request on Trac (just don't expect too much as
> we are currently somewhat understaffed; if you really want that
> feature, asking for advice to help you get it done would give you
> higher chances :).
> 
> (I know we have a ticket for showing percentage of the build, but
> don't know where. This is somewhat related.)
> 
> Mojca

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Feature request

2017-05-05 Thread Mojca Miklavec
On 5 May 2017 at 22:04, rmgls wrote:
> 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:

Yes, it would be nice, but we don'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.

You may open a feature request on Trac (just don't expect too much as
we are currently somewhat understaffed; if you really want that
feature, asking for advice to help you get it done would give you
higher chances :).

(I know we have a ticket for showing percentage of the build, but
don't know where. This is somewhat related.)

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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:
laptops with small ssd for example.


am i wrong?
if i miss something, please let me know.

Thanks.

rmgls
rmgls@



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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
 line
 then I would have known more concisely where I had went wrong.


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.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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 procedure that gets called
in Tcl when an unknown variable or prodeduce is accessed and print a
warning that suggests PortSystem might be missing. Something along the
line of:

 No such variable: configure.agrs, did you forget add PortSystem?

-- 
Clemens Lang

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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.
 
 while this is true, we could still define a procedure that gets called
 in Tcl when an unknown variable or prodeduce is accessed and print a
 warning that suggests PortSystem might be missing. Something along the
 line of:
 
 No such variable: configure.agrs, did you forget add PortSystem?


Or it could be a typo.

Or it could be a command that's only available in trunk and not yet in the 
released version of MacPorts.

I've never heard of anyone putting a line before the PortSystem line, so I 
don't think this is the most common way to reach an error message and so I 
don't think it deserves any special handling by base.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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 current wording confused me, since I have these lines at the top
 of my Portfile:
 
 # $Id: Portfile 86914 2011-11-07 02:04:09Z ecro...@macports.org $
 # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
 c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4
 
 which are obviously not PortSystem.


Thanks, I've made this change.

https://trac.macports.org/changeset/105186


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


suggestion/feature request for Portfile: assert PortSystem comes first

2013-04-11 Thread Roger Pack
Hello.  As a matter of warning newbies like myself, the following occurred.

I added a line to a portfile.  The line was

supported_archs i386

I then ran portindex, and got this:

Failed to parse file multimedia/mplayer-edl-i386/Portfile: invalid
command name supported_archs

(you can guess my 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 more concisely where I had went wrong.

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 current wording confused me, since I have these lines at the top
of my Portfile:

# $Id: Portfile 86914 2011-11-07 02:04:09Z ecro...@macports.org $
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4

which are obviously not PortSystem.

Cheers and thanks.
-roger-
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


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 up to the user to need to 
 figure out how to do that. File tickets in the issue tracker to request such 
 changes to any ports where that makes sense. It's easy to add that to ports 
 now, with the app portgroup.
 
 Wow that is pretty close to what I want.  I was looking for more of a
 create a standalone app (or any way to not pollute /opt/local when
 users install it), though I guess I could use a new macports prefix I
 suppose.

The notion of creating a standalone app is pretty much directly opposite of the 
purpose of MacPorts, which is a good explanation why we don't have such a 
function.

The purpose of MacPorts is to provide an ecosystem of programs and libraries 
that work together.

Standalone app bundles are generally self-contained; if they require 3rd-party 
libraries or frameworks, they're inside the app bundle. Libraries and 
frameworks installed with MacPorts go in ${prefix}/lib and ${frameworks_dir} 
respectively.

Standalone app bundles are expected to be relocatable. Software installed with 
MacPorts usually isn't relocatable, and instead uses absolute paths.

MacPorts ports are designed to be as full-featured as possible; when building a 
standalone app, you usually want the bare minimum of libraries and features 
needed for your app. Optional features of libraries that you're not using would 
be disabled for example. MacPorts doesn't usually provide options to do that, 
because having a greater number of options (variants) increases our support 
burden and usually just ends up confusing users, and makes dependency handling 
more problematic, since we don't have a way to declare dependencies on 
particular variants of ports (ticket #126).

We do have a handful of ports for proper Mac standalone apps, like Adium. 
Ironically this type of software tends to be the hardest for us to create ports 
for, and to keep updated, since they want to link against system libraries, 
want to build against an older SDK in order to be compatible with the largest 
range of OS X versions, want to default to building universal, want to include 
auto-update mechanisms like Sparkle, etc., all of which is the opposite of what 
we want in MacPorts. Really, it'd be best to not have this type of software in 
MacPorts, since it can be installed quite easily simply by downloading it from 
the developer's site. MacPorts is primarily for software whose authors do not 
primarily (or at least not exclusively) target OS X.

I created the app portgroup for software that behaves like a proper Mac app but 
does not create its own app bundle -- primarily software written using libsdl, 
or sometimes Qt. libsdl is a cross-platform library commonly used for games; Qt 
is a cross-platform library often used for non-games. Both libraries contain 
enough Mac-specific code to make programs written using those libraries behave 
like proper Mac apps -- they have a Mac event loop, they show a Mac menu bar, 
they show an icon in the Dock that behaves properly, they have a Quit menu item 
that can quit the app, etc. IIRC Qt usually creates app bundles for you 
already, but libsdl doesn't.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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 the current way seems a bit involved.

If any port reasonably supports being launched as an app bundle, the port 
should install that app bundle. It should not be up to the user to need to 
figure out how to do that. File tickets in the issue tracker to request such 
changes to any ports where that makes sense. It's easy to add that to ports 
now, with the app portgroup.


http://lists.macosforge.org/pipermail/macports-dev/2011-August/015788.html


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


feature request: tell us where the pkg is.

2011-11-25 Thread Roger Pack
Hello.
After running this command:
$ port pkg dos2unix
Warning: MacPorts running without privileges. You may be unable to
complete certain actions (e.g. install).
---  Computing dependencies for dos2unix
---  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:
/Users/rogerdpack/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_dos2unix/dos2unix/work/dos2unix-5.1.1.pkg

But I wouldn't have been able to guess that (I had anticipated it
being put in my pwd, but I guess it isn't).
Thank you.
roger-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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

2011-11-25 Thread Jeremy Lavergne
Right now, all packages are in `port work PORTNAME`.

Roger Pack rogerdpa...@gmail.com wrote:

Hello.
After running this command:
$ port pkg dos2unix
Warning: MacPorts running without privileges. You may be unable to
complete certain actions (e.g. install).
---  Computing dependencies for dos2unix
---  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:
/Users/rogerdpack/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_dos2unix/dos2unix/work/dos2unix-5.1.1.pkg

But I wouldn't have been able to guess that (I had anticipated it
being put in my pwd, but I guess it isn't).
Thank you.
roger-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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

2011-11-25 Thread Ryan Schmidt

On Nov 25, 2011, at 18:28, Roger Pack wrote:

 After running this command:
 $ port pkg dos2unix
 Warning: MacPorts running without privileges. You may be unable to
 complete certain actions (e.g. install).
 ---  Computing dependencies for dos2unix
 ---  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:
 /Users/rogerdpack/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_dos2unix/dos2unix/work/dos2unix-5.1.1.pkg
 
 But I wouldn't have been able to guess that (I had anticipated it
 being put in my pwd, but I guess it isn't).

Yeah I had a bit of head-scratching about that myself the first time I created 
a pkg.

Feel free to file an enhancement request for this in the issue tracker.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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 installed version vs. current one in
ports, etc.

-- 
brandon s allbery                                      allber...@gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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.
That would indeed be user friendlier.

Thanks much!
Sorry if this is a repeat request.
-roger-
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


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, descriptions, etc. It would definitely be beneficial to
automatically offer a basic list of matches in cases like this.
Further fuzziness (suggesting p5-app-ack if the user enters p5-ap-ack,
p5-ack, ack, or even akk) would be even better, but would require the
code to support it, though I wouldn't be surprised if libraries for
this sort of thing already exist.

Actually matching against packages that contain a command has been
suggested I think. The easiest way to do this would be once binary
packages are available. The package contents could be added to a
searchable database.

Good ideas. You might try searching trac.macports.org to see if
they've already been submitted. Submit them yourself if they aren't
already there.

At the least, it'd be a good idea for the error message to suggest
using port search, even if the search isn't automatically run.

-- 
arno  s  hautala    /-|   a...@alum.wpi.edu

pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users