bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #41125] -make documentation is un-installable


From: Richard Frith-Macdonald
Subject: Re: [bug #41125] -make documentation is un-installable
Date: Tue, 7 Jan 2014 14:17:24 +0000

On 7 Jan 2014, at 12:33, Markus Hitter <mah@jump-ing.de> wrote:

>> That would appear to be a different issue.
>> This issue was titled 'make documentation is un-installable'
> 
> Now with being clear the issue actually exists

> and the confusion is more
> a matter of the titles' wording, would you please re-open this bug?

Sorry if it offends, but if there's a different issue, we should address it 
separately rather than re-opening (trying to graft one issue onto another 
invalid one would only cause confusion), as we'd probably need to re-title, 
change the category to be a change request, change the problem description etc.

When you say it's 'clear the issue actually exists'... What issue?

I might guess that the issue you mean is that you want to be able to more 
easily install the gnustep-make documentation without installing gnustep-make?  
If so, perhaps a patch and/or change request to do that would be more 
appropriate?  but where would you install it and why (if you don't have a 
gnustep environment set up, then you really don't have an install location)?

Perhaps I might guess that you mean, as Sebastian suggested, that you want 
documentation to be built and installed along with gnustep-make ... if so, 
that's not a (reasonable IMO) change request ... but since what you are asking 
for is a change to overall policy rather than a specific package, probably the 
mailing list makes more sense.

To be honest though, it looks like you just jumped in at the end of the 
quick-start section in the INSTALL document and are now unhappy because running 
the last bit of the quick-start process without the earlier parts of the 
process didn't do what you expected.
In which case:
a. you aren't likely to do the same thing again and
b. hopefully my changes in trunk will stop anyone else from making the same 
mistake.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]