All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: add comment about ipkg/opkg/rpm
Date: Mon, 24 Aug 2015 22:34:21 +0200	[thread overview]
Message-ID: <20150824203421.GF3619@free.fr> (raw)
In-Reply-To: <55DB7413.4060109@mind.be>

Arnout, All,

On 2015-08-24 21:44 +0200, Arnout Vandecappelle spake thusly:
> On 08/23/2015 11:47 AM, Yann E. MORIN wrote:
> > On 2015-08-23 00:40 +0200, Arnout Vandecappelle spake thusly:
> [snip]
> >>
> >>  Don't know how important this is, but on a 80-character display it gets chopped
> >> off after the faq-no-. But I guess there's not much we can do about it.
> >> Except perhaps: http://nightly.buildroot.org/manual.html#faq-no-binary-packages
> >> - still doesn't fit but at least we get to the binary-pa :-)
> > 
> > What about;
> > 
> >     comment "-----------------------------------------------------"
> >     comment "Please note:                                         "
> >     comment "- Buildroot does *not* generate binary packages,     "
> >     comment "- Buildroot does *not* install any package database. "
> >     comment "*                                                    "
> >     comment "It is up to you to provide those by yourself if you  "
> >     comment "want to use any of those package managers.           "
> >     comment "*                                                    "
> >     comment "See the manual:                                      "
> >     comment "http://buildroot.org/downloads/manual/manaul.html#faq"
> >     comment "-no-binary-packages                                  "
> >     comment "-----------------------------------------------------"
> > 
> > This does fit on a 80-char wide terminal, and we get the complete URL on
> > two lines.
> 
>  ... which is also not ideal, since it means that the URL can't be copy&paste'd
> easily, and that people with a modern terminal that is more than 80 characters
> wide can't ctrl-click (or whatever) to open the URL directly.

Right, but then, it's better than npthing, no?

>  So I think it's best to use the slightly shorter nightly URL and keep it
> non-wrapped.

I would not like we use the nightly version, just because nightly is
not stable.

>  Or actually, it's best to add a manual.html -> downloads/manual/manual.html
> symlink to the website and refer to that. This fits easily:
> http://buildroot.org/manual.html#faq-no-binary-packages
> And it also makes it easier for us to refer to the manual in other places.
> 
>  Peter, what do you think of such a symlink?

At least, I'd like that.

Since I have access to the server, if Peter agrees, I can try to
configure the apache server for that.

But note that this apache server also serves ulibc and busybox.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-08-24 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 15:51 [Buildroot] [PATCH] package: add comment about ipkg/opkg/rpm Yann E. MORIN
2015-08-22 22:40 ` Arnout Vandecappelle
2015-08-23  9:47   ` Yann E. MORIN
2015-08-24 19:44     ` Arnout Vandecappelle
2015-08-24 20:34       ` Yann E. MORIN [this message]
2015-08-25  8:30         ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150824203421.GF3619@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.