Yeah, well, without being told explicitly which package they are in, I have no clue how or where to get them. The debian packaging system is a large black box to me. I have only vague notions of how it works despite doing some reading on it. I barely know what a header is from the C book I picked up 20 blue moons ago. It kind of makes things a lot harder to figure out. And then I'm left wondering why I need a damn "client" when I'm trying to set up a "server." And I have no idea what "development" headers are. It's confusing as hell.
RTFM is all well and good. But when you start mixing and matching technologies and run into edge cases, the manual has limitations unless you have an advanced understanding of what's going on under the hood, which I admittedly do not. Yeah, sure, I could spend a day or two going through in great deal to learn more about the intricacies of the debian packaging system and how it all works, but right now I'm trying to focus on more immediate concerns and learn another technology I'm trying to learn.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
