Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Rainer Müller]

On 2016-08-24 21:40, Mihai Moldovan wrote:
> On 24.08.2016 09:36 PM, Lawrence Velázquez wrote:
>> But those Perl ports are always leaves (w.r.t. `cpuid`) because they are 
>> build dependencies. There's no need to revbump if you're just updating build 
>> dependencies.
> 
> Aren't build dependencies included in the DB? I typically run port_cutleaves 
> -b
> to get rid of leaves minus build dependencies, as these will be needed at some
> point in time again anyway (given I build everything from source.)

port_cutleaves actually takes all of the dependency information from the
PortIndex in the ports tree.

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Lawrence Velázquez]

> On Aug 24, 2016, at 3:40 PM, Mihai Moldovan  wrote:
> 
>> On 24.08.2016 09:36 PM, Lawrence Velázquez wrote:
>> 
>> But those Perl ports are always leaves (w.r.t. `cpuid`) because they are 
>> build dependencies. There's no need to revbump if you're just updating build 
>> dependencies.
> 
> Aren't build dependencies included in the DB?

They are not, at least with trunk.

% port deps clang-3.8
Full Name: clang-3.8 @3.8.1_3+analyzer
Extract Dependencies: subversion, xz
Build Dependencies:   cmake, cctools
Library Dependencies: libxml2, libomp, llvm-3.8, python27, libedit, libffi,
  ncurses, zlib, libcxx
Runtime Dependencies: clang_select, ld64, perl5
%
% (cd ~[mp:base]/src/cregistry && sqlite3 
/opt/local/var/macports/registry/registry.db <<'EOF'
> .load macports.sqlext
> SELECT dependencies.name FROM ports, dependencies WHERE ports.name = 
> 'clang-3.8' AND ports.id = dependencies.id ORDER BY dependencies.name ASC;
> EOF
)
clang_select
ld64
libcxx
libedit
libffi
libomp
libxml2
llvm-3.8
ncurses
perl5
python27
zlib
%

> I typically run port_cutleaves -b to get rid of leaves minus build 
> dependencies, as these will be needed at some point in time again anyway 
> (given I build everything from source.)

I just mark such ports as requested and use "port uninstall 
--follow-dependencies leaves".

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[René J . V . Bertin]

On Wednesday August 24 2016 15:40:27 Lawrence Velázquez wrote:

> > But those Perl ports are always leaves (w.r.t. `cpuid`) because they are 
> > build dependencies. There's no need to revbump if you're just updating 
> > build dependencies.
> 
> To be more specific, there's no need to revbump if the change in build 
> dependencies does not alter the build product.

And in this case there isn't even a need for the dependencies anymore; the new 
version builds fine after I deactivated the ports. Which, btw, didn't raise any 
errors about how `port:cpuid` depended on them. So no, apparently build 
dependencies are not recorded in the DB the same way runtime dependencies are.

>From what I've been able to determine the package needs just *a* perl 
>interpreter >5.8 to execute a build script. The system perl does perfectly 
>fine for that purpose.

R


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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Mihai Moldovan]

On 24.08.2016 09:36 PM, Lawrence Velázquez wrote:
> But those Perl ports are always leaves (w.r.t. `cpuid`) because they are 
> build dependencies. There's no need to revbump if you're just updating build 
> dependencies.

Aren't build dependencies included in the DB? I typically run port_cutleaves -b
to get rid of leaves minus build dependencies, as these will be needed at some
point in time again anyway (given I build everything from source.)

The only way to update this would be a revbump, but if I'm mistaken indeed no
additional work is necessary.



Mihai





signature.asc
Description: OpenPGP digital signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Lawrence Velázquez]

> On Aug 24, 2016, at 3:36 PM, Lawrence Velázquez  wrote:
> 
>> On Aug 24, 2016, at 3:05 PM, Mihai Moldovan  wrote:
>> 
>>> On 24.08.2016 09:02 PM, René J.V. Bertin wrote:
>>> 
>>> Also, cpuid only has a build dependency on 2 perl packages, so there's no 
>>> need to reinstall the port when perl changes.
>> 
>> You can use the revbump to change the dependency to the new perl version, 
>> mainly
>> to make that perl package a leaf. It's not strictly required, but my personal
>> opinion is to do that to enable users to get rid of packages they don't need
>> anymore (and at least I don't like to remove build dependencies, as they 
>> will be
>> pulled in again later anyway.)
> 
> But those Perl ports are always leaves (w.r.t. `cpuid`) because they are 
> build dependencies. There's no need to revbump if you're just updating build 
> dependencies.

To be more specific, there's no need to revbump if the change in build 
dependencies does not alter the build product.

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[René J . V . Bertin]

On Wednesday August 24 2016 21:05:29 Mihai Moldovan wrote:

>Uhm but that won't lead to rebuilds...

But there's no need to rebuild here, just as there wouldn't be a reason to 
rebuild if the perl packages were a runtime dependency.

>to make that perl package a leaf. It's not strictly required, but my personal
>opinion is to do that to enable users to get rid of packages they don't need
>anymore (and at least I don't like to remove build dependencies, as they will 
>be
>pulled in again later anyway.)

Are build dependencies counted in the number of dependents of a port, and if 
so, why. And if so, is that also the case when a port is installed from a 
binary package - and if *that* is not the case, how is that difference 
justified?

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Lawrence Velázquez]

> On Aug 24, 2016, at 3:05 PM, Mihai Moldovan  wrote:
> 
>> On 24.08.2016 09:02 PM, René J.V. Bertin wrote:
>> 
>> Also, cpuid only has a build dependency on 2 perl packages, so there's no 
>> need to reinstall the port when perl changes.
> 
> You can use the revbump to change the dependency to the new perl version, 
> mainly
> to make that perl package a leaf. It's not strictly required, but my personal
> opinion is to do that to enable users to get rid of packages they don't need
> anymore (and at least I don't like to remove build dependencies, as they will 
> be
> pulled in again later anyway.)

But those Perl ports are always leaves (w.r.t. `cpuid`) because they are build 
dependencies. There's no need to revbump if you're just updating build 
dependencies.

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Mihai Moldovan]

On 24.08.2016 09:02 PM, René J.V. Bertin wrote:
> On Wednesday August 24 2016 20:43:08 Mihai Moldovan wrote:
> 
>> It will need a revbump once that's done, but otherwise yes.
> 
> That shouldn't actually be necessary; "base" ought to track which PortGroup 
> files a port depends on, so that portindex can parse them if any of those 
> dependencies change.

Uhm but that won't lead to rebuilds...


> Also, cpuid only has a build dependency on 2 perl packages, so there's no 
> need to reinstall the port when perl changes.

You can use the revbump to change the dependency to the new perl version, mainly
to make that perl package a leaf. It's not strictly required, but my personal
opinion is to do that to enable users to get rid of packages they don't need
anymore (and at least I don't like to remove build dependencies, as they will be
pulled in again later anyway.)



Mihai



signature.asc
Description: OpenPGP digital signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[René J . V . Bertin]

On Wednesday August 24 2016 20:43:08 Mihai Moldovan wrote:

>It will need a revbump once that's done, but otherwise yes.

That shouldn't actually be necessary; "base" ought to track which PortGroup 
files a port depends on, so that portindex can parse them if any of those 
dependencies change.

Also, cpuid only has a build dependency on 2 perl packages, so there's no need 
to reinstall the port when perl changes.

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

Re: [MacPorts] #52081: Ports should require perl5.24 instead of 5.22

[Mihai Moldovan]

On 24.08.2016 08:28 PM, MacPorts wrote:
> #52081: Ports should require perl5.24 instead of 5.22
> Comment (by rjvbertin@…):
> 
>  Not that I can commit it anyway, but I had a look at my `port:cpuid`.
>  Turns out it depends on `port:p${perl5.major}-foo` ; am I right that this
>  means it'll transition as soon as the `perl5.major` variable changes?

It will need a revbump once that's done, but otherwise yes.



Mihai




signature.asc
Description: OpenPGP digital signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev