[prev in list] [next in list] [prev in thread] [next in thread]
List: fink-devel
Subject: Re: [Fink-devel] fink packages dependent on motif officially broken
From: Jack Howarth <howarth.at.fink () gmail ! com>
Date: 2016-10-24 16:37:49
Message-ID: CAP5Ds0DKJypDYr_oRrYrxSY6DL-Et8+S2MN1VRSeTunoO4sdCQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Oct 24, 2016 at 11:06 AM, Alexander Hansen <
alexanderk.hansen@gmail.com> wrote:
>
> On Oct 24, 2016, at 05:59, Jack Howarth <howarth.at.fink@gmail.com> wrote:
>
>
>
> On Sun, Oct 23, 2016 at 8:38 PM, Kevin Horton <khorton01@rogers.com>
> wrote:
>
>> Jack,
>>
>> Thanks for all your work. I'm finally back home today after most of the
>> last two months on the road, and had time to test tracker item 4779, for
>> xephem.
>>
>> I've tested this with fink -m on macOS 10.12, and ran it with XQuartz
>> 2.7.9 and 2.7.10, with no issues. I tried to commit it, but I'm getting
>> "cvs [server aborted]: "commit" requires write access to the repository".
>> I've run out of time to troubleshoot tonight, tomorrow is crazy all day,
>> and I might be on the road again starting Tuesday.
>>
>> I'd appreciate it if someone with working commit privledges could commit
>> the changes in this tracker item.
>>
>
> Unfortunately all of the proposed fixed packaging will have to be revised.
> The fink core developers want to go with the approach of entirely replacing
> the libXt from Xquartz with their own libxt and libxt-flat BuildDependOnly
> packages that install in %p. This will require all packages that link libXt
> to either BuildDepends/Depends on libxt/libxt-shlibs or
> libxt-flat/libxt-flat-shlibs.
> Jack
> ps I have serious reservations about this approach as it potentially will
> make builds of packages that aren't updated properly non-deterministic in
> that the libXt used for linkage could either be from libxt or libxt-flat
> depending upon what happens to be installed at the time of the build.
>
>
> How? If libxt and libxt-flat are mutually conflicting BuildDepends, as
> they should be, then only one form _can_ be installed at the time of the
> build.
>
My point is, unless we strictly enforce the usage of BuildDepends on libxt
for non-motif x11 packages, we run the risk of accidental non-deterministic
builds. We have a hard enough time getting developers to bother to run
'fink -m' on their packages, never mind asking them to manually search for
linkages of binaries on libXt in order to determine if the explicit libxt
BuildDepends is required in addition to x11-dev.
>
> The possibility of picking up libXt from Xquartz exists of course, but we
> can handle that the same way as we handle the possibility of builds picking
> up libping, freetype, … from Xquartz.
>
> Also requiring all of the developers to find the libXt linkages in
> binaries on their on, without a reminder from 'fink validate', seems like a
> heavy lift.
>
>
>
> Are there that many, really?
>
> --
> Alexander Hansen, Ph.D.
> Fink User Liaison
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct \
24, 2016 at 11:06 AM, Alexander Hansen <span dir="ltr"><<a \
href="mailto:alexanderk.hansen@gmail.com" \
target="_blank">alexanderk.hansen@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span \
class=""><blockquote type="cite"><div>On Oct 24, 2016, at 05:59, Jack Howarth <<a \
href="mailto:howarth.at.fink@gmail.com" \
target="_blank">howarth.at.fink@gmail.com</a>> wrote:</div><br \
class="m_1940615693381991895Apple-interchange-newline"><div><div dir="ltr"><br><div \
class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 23, 2016 at 8:38 PM, \
Kevin Horton <span dir="ltr"><<a href="mailto:khorton01@rogers.com" \
target="_blank">khorton01@rogers.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div style="word-wrap:break-word"><div \
style="word-wrap:break-word">Jack,<div><br></div><div><span><div>Thanks for all your \
work. I'm finally back home today after most of the last two months on the \
road, and had time to test tracker item 4779, for \
xephem.</div><div><br></div><div>I've tested this with fink -m on macOS 10.12, \
and ran it with XQuartz 2.7.9 and 2.7.10, with no issues. I tried to commit it, but \
I'm getting "cvs [server aborted]: "commit" requires write access \
to the repository". I've run out of time to troubleshoot tonight, tomorrow is crazy \
all day, and I might be on the road again starting \
Tuesday.</div><div><br></div><div>I'd appreciate it if someone with working \
commit privledges could commit the changes in this tracker item. \
</div></span></div></div></div></blockquote><div><br></div><div>Unfortunately all of \
the proposed fixed packaging will have to be revised. The fink core developers want \
to go with the approach of entirely replacing the libXt from Xquartz with their own \
libxt and libxt-flat BuildDependOnly packages that install in %p. This will require \
all packages that link libXt to either BuildDepends/Depends on libxt/libxt-shlibs or \
libxt-flat/libxt-flat-shlibs.</div><div> Jack</div><div>ps I have \
serious reservations about this approach as it potentially will make builds of \
packages that aren't updated properly non-deterministic in that the libXt used \
for linkage could either be from libxt or libxt-flat depending upon what happens to \
be installed at the time of the build. \
</div></div></div></div></div></blockquote><div><br></div></span><div>How? If libxt \
and libxt-flat are mutually conflicting BuildDepends, as they should be, then only \
one form _can_ be installed at the time of the build. \
</div></div></div></blockquote><div><br></div><div>My point is, unless we strictly \
enforce the usage of BuildDepends on libxt for non-motif x11 packages, we run the \
risk of accidental non-deterministic builds. We have a hard enough time getting \
developers to bother to run 'fink -m' on their packages, never mind asking \
them to manually search for linkages of binaries on libXt in order to determine if \
the explicit libxt BuildDepends is required in addition to x11-dev.</div><div> \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div \
style="word-wrap:break-word"><div><div><br></div><div>The possibility of picking up \
libXt from Xquartz exists of course, but we can handle that the same way as we handle \
the possibility of builds picking up libping, freetype, … from Xquartz.</div><span \
class=""><br><blockquote type="cite"><div><div dir="ltr"><div \
class="gmail_extra"><div class="gmail_quote"><div>Also requiring all of the \
developers to find the libXt linkages in binaries on their on, without a reminder \
from 'fink validate', seems like a heavy lift.</div><div> \
</div></div></div></div></div></blockquote><br></span></div><div>Are there that many, \
really? </div><span class="HOEnZb"><font color="#888888"><br><div> <div>-- \
<br>Alexander Hansen, Ph.D.<br>Fink User Liaison</div>
</div>
<br></font></span></div></blockquote></div><br></div></div>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic