Re: Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-04-11 Thread MK-MacPorts
On 21 Mar 2014, at 00:14 , Ryan Schmidt ryandes...@macports.org wrote:
 I’m not aware of any ports that do that, or any tests that are designed to 
 work that way.

Only recently I came across the test phase” which can be defined in a portfile.

I’ve introduced properly running tests for kmymoney4-devel with r118839.
The user can build and run the tests by using this sequence:
—
$ sudo port test kmymoney4-devel +tests
—

Afterwards the user could proceed with
—
$ sudo port install kmymoney4-devel +tests
—
without the tests actually being installed in the system, which the “tests” 
variant might imply.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-04-11 Thread Eric Gallager
On Fri, Apr 11, 2014 at 6:52 PM, mk-macpo...@techno.ms wrote:

 On 21 Mar 2014, at 00:14 , Ryan Schmidt ryandes...@macports.org wrote:
  I'm not aware of any ports that do that, or any tests that are designed
 to work that way.

 Only recently I came across the test phase which can be defined in a
 portfile.

 I've introduced properly running tests for kmymoney4-devel with r118839.
 The user can build and run the tests by using this sequence:
 --
 $ sudo port test kmymoney4-devel +tests
 --


Yeah, I have noticed that my Portfiles with test phases usually end up with
the test phase hidden in a variant like that as well, although in my case
it is usually because there is no way to specify dependencies needed just
for the test phase: https://trac.macports.org/ticket/38208 (which is why I
just stick them in a variant instead)


 Afterwards the user could proceed with
 --
 $ sudo port install kmymoney4-devel +tests
 --
 without the tests actually being installed in the system, which the
 tests variant might imply.


The issue for tests not actually being part of the normal install process
is https://trac.macports.org/ticket/42731
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-04-11 Thread MK-MacPorts
Hi Eric,

thanks for letting me know about those two tickets, to which I CC’ed myself 
just now. :-)

I am not so sure that you can actually INSTALL all tests with any software… 
independent on whether you actually might now want to do that. The 
two-step-install I use with kmymoney4-devel +tests is perhaps not so nice 
during install, but at least it does what I intended to do.

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-03-20 Thread MK-MacPorts
I would like to introduce a tests variant for a port.

Can someone point me to a port which successfully installs a test variant?

I know that I can build and run tests when building ports (i.e. when I only run 
“sudo port build; cd build; ctest …”).

But I want that all needed test files get actually installed in the system and 
not only built and removed again.
So, I’d like to know where to place which files below ${destroot}.

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-03-20 Thread Ryan Schmidt

On Mar 20, 2014, at 03:07, mk-macpo...@techno.ms wrote:

 I would like to introduce a tests variant for a port.
 
 Can someone point me to a port which successfully installs a test variant?
 
 I know that I can build and run tests when building ports (i.e. when I only 
 run “sudo port build; cd build; ctest …”).
 
 But I want that all needed test files get actually installed in the system 
 and not only built and removed again.
 So, I’d like to know where to place which files below ${destroot}.

I’m not aware of any ports that do that, or any tests that are designed to work 
that way.

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


Re: Where do I find a good example of a tests variant (which is really installing the tests on the system)?

2014-03-20 Thread MK-MacPorts
On 21 Mar 2014, at 00:14 , Ryan Schmidt ryandes...@macports.org wrote:
 I’m not aware of any ports that do that, or any tests that are designed to 
 work that way.

OK, in just now I have made it work by simply chown'ing the port’s work 
directory and executing ctest by the logged in user.
That finally did the job.

(And yes, you are right, the tests wouldn’t work if one would install the tests 
someplace.
The test apps need to sit in the build directory in order to access additional 
files outside it.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev