On Wed, Dec 14, 2005 at 09:54:06PM +, Ciaran McCreesh wrote:
On Wed, 14 Dec 2005 13:48:45 -0800 Zac Medico [EMAIL PROTECTED] wrote:
| I wish you'd reconsider, because I was looking forward to multiple
| repository support.
Well, if Portage ever gets multiple repository support, then news
On Sun, Dec 18, 2005 at 01:07:27AM +, Ciaran McCreesh wrote:
On Sat, 17 Dec 2005 16:51:05 -0800 Brian Harring [EMAIL PROTECTED]
wrote:
| Transitioning from single news.unread to N is going to break clients
| that expect a single.
Yup.
| As I said, you're going to break stuff- and
On Wednesday 14 December 2005 09:52, Ciaran McCreesh wrote:
On Wed, 14 Dec 2005 09:11:51 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| newsdir=$(portageq envvar PORTDIR)/metadata/news
| newsdir=$(portageq newsdir gentoo)
|
| Both have one level of indirection. The first has two hard coded
On Wed, 14 Dec 2005 21:09:02 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| What's a 'PORTDIR'?
A PORTDIR is a well defined, widely used variable.
| What's a 'metadata'?
A metadata is a well defined, widely used directory in the tree.
| Outside of portage, these are also magic name voodoo.
Ciaran McCreesh wrote:
| soon. The solution to that seems simple to me. Rather than have
| 'package manager' do anything, just have it provide hooks that will
| allow you to do your thing at the times you want.
Exactly what I am doing. Hence why I'm not making Portage know any more
than it
On Wed, 14 Dec 2005 13:48:45 -0800 Zac Medico [EMAIL PROTECTED] wrote:
| I wish you'd reconsider, because I was looking forward to multiple
| repository support.
Well, if Portage ever gets multiple repository support, then news
clients can be updated to handle it. The GLEP says that already.
--
On Tuesday 13 December 2005 11:45, Andrew Muraco wrote:
Jason Stubbs wrote:
On Tuesday 13 December 2005 11:22, Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 11:17:30 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| So what are you going to do? I asked already but you didn't answer.
| How are you
On Tuesday 13 December 2005 11:48, Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 11:39:14 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| And how can that be adapted to work with overlays, completely
| ignoring the possibility of distinct repositories. Overlays is
| something that exists already
Jason Stubbs wrote: [Mon Dec 12 2005, 07:51:51PM CST]
| There doesn't need to be a debate. This whole proposal doesn't care
| about portage compatibility whatsoever and it's exactly this style of
| thinking that slows down portage development (which everybody loves
| to complain about so
On Wednesday 14 December 2005 07:12, Grant Goodyear wrote:
Jason Stubbs wrote: [Mon Dec 12 2005, 07:51:51PM CST]
| As I said already, there will immediately be a bug asking for overlay
| support. Portage already supports multiple in a form whether anybody
| likes it or not. How they are
On Wed, 14 Dec 2005 08:44:39 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| Modifications are required to portage anyway. Why postpone it until
| after several readers are written and force all of them become broken?
Because there isn't a specification saying what the future changes to
Portage
Jason Stubbs wrote: [Tue Dec 13 2005, 05:44:39PM CST]
Wouldn't it suffice for the GLEP to simply have a statement that it will
query portage for a list of repositories, once there's a way to do that,
but until then the default repo will be assumed?
Modifications are required to portage
On Wednesday 14 December 2005 08:54, Ciaran McCreesh wrote:
On Wed, 14 Dec 2005 08:44:39 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| Modifications are required to portage anyway. Why postpone it until
| after several readers are written and force all of them become broken?
Because there
On Wed, 14 Dec 2005 09:11:51 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| newsdir=$(portageq envvar PORTDIR)/metadata/news
| newsdir=$(portageq newsdir gentoo)
|
| Both have one level of indirection. The first has two hard coded
| elements. The first has one. Where is the massive
For reference, I'm quoting this snippet from earlier in the thread:
Jason Stubbs wrote:
On Sunday 11 December 2005 10:35, Ciaran McCreesh wrote:
.. Note:: Future changes to Portage involving support for multiple
repositories may require one news list per repository. Assuming
repositories have
Ciaran McCreesh posted [EMAIL PROTECTED], excerpted
below, on Sun, 11 Dec 2005 21:19:08 +:
Does anyone really use emerge --ask?
Oh, /my/ yes!
The following should speak for itself. (I have a similar set of ep*
commands, those in /usr/local/bin, so I can --pretend as my normal user.
Yes,
Jason Stubbs posted [EMAIL PROTECTED], excerpted
below, on Mon, 12 Dec 2005 09:11:53 +0900:
On Monday 12 December 2005 09:01, Ciaran McCreesh wrote:
On Mon, 12 Dec 2005 08:44:00 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| Repositories will be user-labelled. However, all that readers need
On Mon, 12 Dec 2005 23:49:31 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| No need for a glep as far as portage support goes anymore than Ciaran
| needs a glep to change or add syntax highlighting in vim.
The difference is, Vim syntax scripts are well established, and there
aren't any design
On Tuesday 13 December 2005 02:16, Ciaran McCreesh wrote:
On Mon, 12 Dec 2005 23:49:31 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| No need for a glep as far as portage support goes anymore than Ciaran
| needs a glep to change or add syntax highlighting in vim.
The difference is, Vim
On Tue, 13 Dec 2005 10:51:51 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| Without a list of future features, you think the best way to go must
| be the least agile? As Zac said, all that matters to keep full
| compatibility on the side of the readers is to add a level of
| indirection. All your
On Tuesday 13 December 2005 11:11, Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 10:51:51 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| Without a list of future features, you think the best way to go must
| be the least agile? As Zac said, all that matters to keep full
| compatibility on the
On Tue, 13 Dec 2005 11:17:30 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| So what are you going to do? I asked already but you didn't answer.
| How are you going to find $PORTDIR/metadata/news?
At present, by using portageq with a hardcoded suffix. If in the future
Portage introduces new
On Tuesday 13 December 2005 11:22, Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 11:17:30 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| So what are you going to do? I asked already but you didn't answer.
| How are you going to find $PORTDIR/metadata/news?
At present, by using portageq with a
Jason Stubbs wrote:
On Tuesday 13 December 2005 11:22, Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 11:17:30 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| So what are you going to do? I asked already but you didn't answer.
| How are you going to find $PORTDIR/metadata/news?
At present, by
Ciaran McCreesh wrote:
On Tue, 13 Dec 2005 11:39:14 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| And how can that be adapted to work with overlays, completely
| ignoring the possibility of distinct repositories. Overlays is
| something that exists already and news support for them is a request
Point of Clarity,
and the ``mysql-5`` database format changes.
These changes actually occured in mysql 4.1, not mysql-5
On 12/10/05, Ciaran McCreesh [EMAIL PROTECTED] wrote:
Main changes since the previous edition:
* File format tweaks.
* Changes to the way relevance headers work to make
On Sat, 2005-12-10 at 22:31 -0500, Dan Meltzer wrote:
Point of Clarity,
and the ``mysql-5`` database format changes.
These changes actually occured in mysql 4.1, not mysql-5
* The sender's first name ends in 'an', and they are not me.
Um, your first name ends in 'an' so your
27 matches
Mail list logo
