From: Alistair Bush <ali_bush@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] .la files removal news item (GLEP 42)
Date: Sat, 2 Oct 2010 10:20:11 +1300 [thread overview]
Message-ID: <201010021020.11925.ali_bush@gentoo.org> (raw)
In-Reply-To: <4CA5B7A4.6060203@gentoo.org>
> Hi lads,
> due to recent situation about .la files status we would like to inform
> users about this situation. See attached file that we propose to be
> included as news item.
>
Would it not be a better solution to have this information documented
"properly" under Upgrade Guides or Gentoo System Documentation and then have
this news item linked to it.
What i'm concerned about is that this is not really a news item. From what I
understand this issue could be with us for a rather long time (years even)
so...
How is this news item going to help ppl in a month from now (till the issue is
solved in its entirety).
Can we reasonably expect a new user to be aware of this. Do we expect users
to read old ( and this could potentially become very old) news items.
This is potentually a different situation from someone updating dbus (for
example) from <y.y.y to >=y.y.y and having a once off (fire and forget)
migration task. It is for this reason that I think this should be documented.
Alistair.
> Step 2 will be finding global policy how to get rid of them as fast as
> possible without too much more hassle for our users :)
>
> --------
> Tomáš Chvátal
> Gentoo Linux Developer [Clustering/Council/KDE/QA/Sci/X11]
> E-Mail : scarabeus@gentoo.org
> GnuPG FP : 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587
> GnuPG ID : 03414587
next prev parent reply other threads:[~2010-10-01 21:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 10:27 [gentoo-dev] .la files removal news item (GLEP 42) Tomáš Chvátal
2010-10-01 11:49 ` "Paweł Hajdan, Jr."
2010-10-01 13:31 ` Peter Volkov
2010-10-01 15:04 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-01 15:42 ` Eray Aslan
2010-10-01 18:02 ` Diego Elio Pettenò
2010-10-01 19:22 ` Enrico Weigelt
2010-10-02 1:02 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-02 15:30 ` [gentoo-dev] " Peter Volkov
2010-10-01 15:13 ` [gentoo-dev] " Nirbheek Chauhan
2010-10-01 15:33 ` Zac Medico
2010-10-01 15:43 ` Nirbheek Chauhan
2010-10-01 17:54 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-01 19:12 ` Nirbheek Chauhan
2010-10-01 19:38 ` Zac Medico
2010-10-01 21:10 ` Nirbheek Chauhan
2010-10-01 21:32 ` Zac Medico
2010-10-02 12:21 ` Peter Volkov
2010-10-02 17:43 ` Zac Medico
2010-10-02 19:31 ` Peter Volkov
2010-10-02 1:06 ` [gentoo-dev] " Diego Elio Pettenò
2010-10-02 5:40 ` [gentoo-dev] " Duncan
2010-10-02 12:00 ` Dale
2010-10-02 15:51 ` Luca Barbato
2010-10-02 16:26 ` Nirbheek Chauhan
2010-10-03 14:11 ` Luca Barbato
2010-10-03 14:54 ` Nirbheek Chauhan
2010-10-01 21:20 ` Alistair Bush [this message]
2010-10-02 3:01 ` [gentoo-dev] " Donnie Berkholz
2010-10-02 13:07 ` Jorge Manuel B. S. Vicetto
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=201010021020.11925.ali_bush@gentoo.org \
--to=ali_bush@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox