[arch-general] xterm and xorg-apps

Andrew Przepioski aprzepioski at gmail.com
Wed Feb 18 15:24:28 EST 2009


On 2/18/09, Grigorios Bouzakis <grbzks at gmail.com> wrote:
> On Wed, Feb 18, 2009 at 9:43 PM, Andrew Przepioski
> <aprzepioski at gmail.com> wrote:
>> On 2/18/09, Andrew Przepioski <aprzepioski at gmail.com> wrote:
>>> On 2/18/09, Grigorios Bouzakis <grbzks at gmail.com> wrote:
>>>> On Wed, Feb 18, 2009 at 01:19:18PM -0600, Aaron Griffin wrote:
>>>>> On Wed, Feb 18, 2009 at 1:12 PM, Andrew Przepioski
>>>>> <aprzepioski at gmail.com> wrote:
>>>>> > To me, when I was googling about xterm trying to
>>>>> > determine why xorg-apps was included, what feature is included with
>>>>> > xterm that makes it need xorg-apps, I couldn't find anything
>>>>>
>>>>> Might be helpful to use namcap in cases like this (gmail will probably
>>>>> wrap the output below). Though in the case of xterm, it doesn't help
>>>>> us - svn logs would be the next best bet
>>>>>
>>>>> $ namcap -i /var/cache/pacman/pkg/xterm-241-1-x86_64.pkg.tar.gz
>>>>> xterm      E: Dependency detected and not included (libxmu) from files
>>>>> ['usr/bin/xterm']
>>>>> xterm      E: Dependency detected and not included (bash) from files
>>>>> ['usr/bin/koi8rxterm', 'usr/bin/uxterm']
>>>>> xterm      W: Dependency included and not needed (libxaw)
>>>>> xterm      W: Dependency included but already satisfied (ncurses)
>>>>> xterm      W: Dependency included and not needed (xorg-apps)
>>>>> xterm      I: Script link detected (bash) in file
>>>>> ['usr/bin/koi8rxterm', 'usr/bin/uxterm']
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on libxmu
>>>>> xterm      I: File ['usr/bin/xterm', 'usr/bin/resize'] link-level
>>>>> dependence on ncurses
>>>>> xterm      I: File ['usr/bin/xterm', 'usr/bin/resize'] link-level
>>>>> dependence on glibc
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on libx11
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on
>>>>> fontconfig
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on libice
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on libxt
>>>>> xterm      I: File ['usr/bin/xterm'] link-level dependence on libxft
>>>>> xterm      I: File ['usr/bin/koi8rxterm', 'usr/bin/uxterm'] link-level
>>>>> dependence on bash
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (zlib)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (expat)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxcb)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (inputproto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxau)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (tzdata)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxdmcp)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (renderproto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (glibc)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (fontconfig)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libice)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxt)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxext)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (kbproto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (xextproto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (ncurses)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (xproto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (xcb-proto)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (readline)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (kernel-headers)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (freetype2)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libx11)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (e2fsprogs)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libxrender)
>>>>> xterm      I: Dependency covered by dependences from link dependence
>>>>> (libsm)
>>>>> xterm      I: Depends as namcap sees them: depends=(libxmu bash libxft)
>>>>> xterm      E: Missing license
>>>>
>>>> See my comments on http://bugs.archlinux.org/task/7781
>>>> I dont know if google returns results like these, but the bug tracker
>>>> search does if you look for xorg-apps, or xterm.
>>>> xorg-apps were a dependency for xterm before 230, even if it was
>>>> uneeded,
>>>> it is also one today.
>>>>
>>>> --
>>>> Greg
>>>>
>>>
>>> Yeah, I bumped into link when I was searching, but it doesn't mention
>>> anywhere exactly why xorg-apps is needed for xterm. From what I can
>>> see, it just mentions at one part that xorg-apps is a dependency of
>>> xterm and would automatically come with it.
>>>
>>> "Note: "xorg-apps" will be automatically installed as a dependency of
>>> "xterm", but I assume that implicitly relying on this sub-dependency
>>> to continue to exist in the future would be less preferable than
>>> listing it explicitly."
>>>
>>
>> Ah! My bad! I didn't see it down there. :\
>>
>
> If you dont like the dependency that much, or need space or whatever and
> dont
> want to build your own package, you can pacman -Rd xorg-apps. xterm doesnt
> need xmessage. Only koi8xterm does.
>
> --
> Greg
>

Like I said earlier, I just do pacman -Sd xterm because by the time I
am installing pacman, I already satisfy the other dependencies and I
knew that I didn't use xorg-apps or the feature in xterm that needed
xorg-apps, and I was just curious as to what feature of xterm needed
xorg-apps. Now I know it's xmessages.

Hehe, next time I'll have to read more carefully though because now I
see that you clearly said it on the bug report and I just completely
ignored the comment section at the bottom, haha, and now I know about
numcap, which will hopefully make it easier for me to find the answer
to this kind of question next time I notice a dependency that I am not
too sure of.

Thank-you. :)


More information about the arch-general mailing list