Re: Readline clashes with stow. How should I resolve them?

James Jong <[email protected]> Wed, 24 Apr 2013 11:53:21 -0400
Newsgroups gmane.comp.gnu.stow.general
Message-ID <CAD4ivxWu86X8uwFwEzENpLYTLAE-7v+T3PA7ngGPTWMPOC_2XQ@mail.gmail.com>
--047d7b343e345c560404db1d4e5f
Content-Type: text/plain; charset=ISO-8859-1

I just built the latest version from master and read about the override
option. I tried

stow --override=dir readline-6.2
and
stow --override=info readline-6.2

but I still get the following WARNING which suggests that stow still
clashes with readline:

existing target is stowed to a different package: share/info/dir =>
../../../../../../n/124/opt/stow_all/stow/stow-cvs+git-189-g20d3759/share/info/dir
All operations aborted.

Any thoughts why? Thanks again for all your help.

James


On Wed, Apr 24, 2013 at 9:50 AM, James Jong <[email protected]> wrote:

> Thank you Adam. I presume that there is no way to simply ask stow to
> overwrite the symlinks when there is a conflict (this way I would not need
> to touch anything in the original package directories in the stow
> directory). Is this correct?
>
> Sorry about the double posting - I usually post in StackExchange first and
> later in an email list with a link to the question if I conclude the mail
> list is a better place, but this time I went the other way around. My
> apologies.
>
> Thanks again,
> James
>
>
>
>
>
> On Wed, Apr 24, 2013 at 3:57 AM, Adam Spiers <[email protected]> wrote:
>
>> On Mon, Apr 22, 2013 at 08:21:04PM -0400, James Jong wrote:
>> > I tried to stow readline-6.2 and got the following WARNING:
>> >
>> > ==============================
>> > > stow readline-6.2
>> > Loading defaults from /home/josh/.stowrc
>> > WARNING! stowing readline-6.2 would cause conflicts:
>> >   * existing target is stowed to a different package: share/info/dir =>
>> > ../../../stow_storage/stow_2.2.0_canonical_paths/share/info/dir
>> > All operations aborted.
>> > ==============================
>> >
>> > Here is is what that existing target contains:
>> > ==============================
>> > > cat ~/local/share/info/dir
>> > This is the file .../info/dir, which contains the
>> > topmost node of the Info hierarchy, called (dir)Top.
>> > The first time you invoke Info you start off looking at this node.
>> >
>> > File: dir,      Node: Top       This is the top of the INFO tree
>> >
>> >   This (the Directory node) gives a menu of major topics.
>> >   Typing "q" exits, "?" lists all Info commands, "d" returns here,
>> >   "h" gives a primer for first-timers,
>> >   "mEmacs<Return>" visits the Emacs manual, etc.
>> >
>> >   In Emacs, you can click mouse button 2 on a menu item or cross
>> reference
>> >   to select it.
>> >
>> > * Menu:
>> >
>> > System administration
>> > * Stow: (stow).                 GNU Stow.
>> > ==============================
>> >
>> > How can I resolve this?
>>
>> I see that this has already been answered here:
>>
>>
>> http://unix.stackexchange.com/questions/73426/dealing-with-gnu-stow-conflicts
>>
>> The respondent is correct that you can simply delete the 'dir' file
>> from within the Stow package prior to stowing.  Alternatively you can
>> skip the install-info target of the package's Makefile if the package
>> allows it.  The Info 'dir' file is (by design) conceptually owned by
>> all packages which contribute to its contents, and Stow does not yet
>> support hooks which could allow automated manipulation of its contents
>> in this fashion.  However this issue also affects me, so I have added
>> it to the TODO, and there is a reasonable chance I will implement it
>> at some point (although pull requests are highly encouraged if you
>> want it sooner).
>>
>> Finally, if you are going to duplicate-post the same question in
>> multiple locations (e.g. on one of the Stow lists and on
>> StackExchange), then please explicitly cross-link from each
>> post/thread to the other.  Otherwise you risk wasting someone's time
>> when they reply to a question which has already been answered
>> elsewhere.
>>
>> Regards,
>> Adam
>>
>>
>

--047d7b343e345c560404db1d4e5f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>I just built the latest version from m=
aster and read about the override option. I tried<br><br></div>stow --overr=
ide=3Ddir readline-6.2 <br></div><div>and<br>stow --override=3Dinfo readlin=
e-6.2 <br>


</div><br>but I still get the following WARNING which suggests that stow st=
ill clashes with readline:<br><br>existing target is stowed to a different =
package: share/info/dir =3D&gt; ../../../../../../n/124/opt/stow_all/stow/s=
tow-cvs+git-189-g20d3759/share/info/dir<br>


All operations aborted.<br><br></div>Any thoughts why? Thanks again for all=
 your help. <br><br></div>James<br>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Apr 2=
4, 2013 at 9:50 AM, James Jong <span dir=3D"ltr">&lt;<a href=3D"mailto:ribo=
[email protected]" target=3D"_blank">[email protected]</a>&gt;</span>=
 wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>Thank you Adam. I=
 presume that there is no way to simply ask stow to overwrite the=20
symlinks when there is a conflict (this way I would not need to touch anyth=
ing in the original=20
package directories in the stow directory). Is this correct?<br><br>Sorry a=
bout the double posting - I usually post in StackExchange first and later i=
n an email list with a link to the question if I conclude the mail list is =
a better place, but this time I went the other way around. My apologies.<br=
>



<br></div>Thanks again,<br></div><div>James<br></div><div><br></div><div><d=
iv><br><br></div></div></div><div><div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Wed, Apr 24, 2013 at 3:57 AM, Adam Spiers <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">=
[email protected]</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div>On Mon, Apr 22, 2013 at 08:21:04PM=
 -0400, James Jong wrote:<br>
&gt; I tried to stow readline-6.2 and got the following WARNING:<br>
&gt;<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>
&gt; &gt; stow readline-6.2<br>
&gt; Loading defaults from /home/josh/.stowrc<br>
&gt; WARNING! stowing readline-6.2 would cause conflicts:<br>
&gt; =A0 * existing target is stowed to a different package: share/info/dir=
 =3D&gt;<br>
&gt; ../../../stow_storage/stow_2.2.0_canonical_paths/share/info/dir<br>
&gt; All operations aborted.<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; Here is is what that existing target contains:<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>
&gt; &gt; cat ~/local/share/info/dir<br>
&gt; This is the file .../info/dir, which contains the<br>
&gt; topmost node of the Info hierarchy, called (dir)Top.<br>
&gt; The first time you invoke Info you start off looking at this node.<br>
&gt;<br>
&gt; File: dir, =A0 =A0 =A0Node: Top =A0 =A0 =A0 This is the top of the INF=
O tree<br>
&gt;<br>
&gt; =A0 This (the Directory node) gives a menu of major topics.<br>
&gt; =A0 Typing &quot;q&quot; exits, &quot;?&quot; lists all Info commands,=
 &quot;d&quot; returns here,<br>
&gt; =A0 &quot;h&quot; gives a primer for first-timers,<br>
&gt; =A0 &quot;mEmacs&lt;Return&gt;&quot; visits the Emacs manual, etc.<br>
&gt;<br>
&gt; =A0 In Emacs, you can click mouse button 2 on a menu item or cross ref=
erence<br>
&gt; =A0 to select it.<br>
&gt;<br>
&gt; * Menu:<br>
&gt;<br>
&gt; System administration<br>
&gt; * Stow: (stow). =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 GNU Stow.<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; How can I resolve this?<br>
<br>
</div></div>I see that this has already been answered here:<br>
<br>
=A0 <a href=3D"http://unix.stackexchange.com/questions/73426/dealing-with-g=
nu-stow-conflicts" target=3D"_blank">http://unix.stackexchange.com/question=
s/73426/dealing-with-gnu-stow-conflicts</a><br>
<br>
The respondent is correct that you can simply delete the &#39;dir&#39; file=
<br>
from within the Stow package prior to stowing. =A0Alternatively you can<br>
skip the install-info target of the package&#39;s Makefile if the package<b=
r>
allows it. =A0The Info &#39;dir&#39; file is (by design) conceptually owned=
 by<br>
all packages which contribute to its contents, and Stow does not yet<br>
support hooks which could allow automated manipulation of its contents<br>
in this fashion. =A0However this issue also affects me, so I have added<br>
it to the TODO, and there is a reasonable chance I will implement it<br>
at some point (although pull requests are highly encouraged if you<br>
want it sooner).<br>
<br>
Finally, if you are going to duplicate-post the same question in<br>
multiple locations (e.g. on one of the Stow lists and on<br>
StackExchange), then please explicitly cross-link from each<br>
post/thread to the other. =A0Otherwise you risk wasting someone&#39;s time<=
br>
when they reply to a question which has already been answered<br>
elsewhere.<br>
<br>
Regards,<br>
Adam<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>

--047d7b343e345c560404db1d4e5f--