Menu

#1352 STOPS BUILDS, is "integrated" into X11R7 and GLIBC, PHONES HOME

packaging problem
pending-invalid
5
2014-12-18
2014-12-15
No

BUILDS FAIL
BUILDS FAIL
BUILDS FAIL

PHONE HOME SOFTWARE
PHONE HOME SOFTWARE
PHONE HOME SOFTWARE

do not like the way it has been injected into X11R7 and GCC builds

1) no tarball to dowload that builds and installs. all scattered and bull install. the is no make and ? install scripts ? install interactively to user HOME. this is far from working during a build. VERY FAR.

2) xmlto phones home during make(1) for files even if installed by hand (no way to know why it is doing so)

i like the project but the fact of it PREVENT NORMAL MANPAGE BUILDING (by injecting itself as producer of manpages, which had already been working w/o xml, yet not being ready to do so) and REQUIRING PARTS into X11R7 w/o any way for one building to do so (other than use hugely bloated distro packages which are unusable if one is compiling gcc)

it dawns upon me that whoever is managing this KNOWS it's a "dependancy" and knows broken dependancies are a hold up for everyone

moreso, to compile glibc also, someone has hacked in dependancies from X11R7 (ie, fonts), which includes xmlto (possibly skipped, but some sgml xml things for X cannot be - to build glibc, libc)

this is getting tiresome where one cannot build CORE SOFTWARE without some comittee hack wares that have ZERO AND NOTHING to do with the task make(1) is running to make

even more insulting is some euro comittee who's being paid, i am not, is making my life harder and adding nothing i need. if i'm building libc it's for C, not for euro comittee wishes. i don't care what they wish for nor what they demand.

unless it builds without trouble, which IT ABSOLUTELY DOES NOT DO

PHONE HOME SOFTWARE
PHONE HOME SOFTWARE
PHONE HOME SOFTWARE

BUILDS FAIL
BUILDS FAIL
BUILDS FAIL

Discussion

  • Robert Stayton

    Robert Stayton - 2014-12-18
    • status: open --> pending-invalid
    • assigned_to: Robert Stayton
     
  • Robert Stayton

    Robert Stayton - 2014-12-18

    I think this bug report was entered in the wrong project. This report does not seem to have anything to do with DocBook.