public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Remaining PMS todo list etc
Date: Wed, 19 Mar 2008 18:27:17 +0000	[thread overview]
Message-ID: <20080319182717.69c0f975@snowcone> (raw)

[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]

There's an updated, pre-built copy of current PMS at:

    http://dev.gentoo.org/~spb/pms.pdf

And source at:

    http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git

And "PMS for people who haven't been paying attention" at:

    http://archives.gentoo.org/gentoo-dev/msg_4ac035019b5264e5b9c176493bcc6b5b.xml

And an explanation of kdebuild at:

    http://archives.gentoo.org/gentoo-dev/msg_0594dd89e411526c2a68cae9916c6a16.xml

And the following note about bugs: Please stop making bugs with
[EAPI-2] or whatever in the title. Use [Future EAPI] unless you have a
definite agreement from absolutely everybody and their dog that it's
going into EAPI 2. I had to go through and fix a load of bugs saying
[EAPI 1] and don't really want to do it again.

Things still left to do for PMS are as follows. Well-informed people
are encouraged to comment and provide patches to pms-bugs@g.o. If you
aren't sure whether you're well-informed, you aren't.

* Someone needs to write up dohtml.

* 178092: Someone needs to write up package.use.

* 170697: can we consider profile masks to be in the same category as
  'use? ( ) : ( )' and thus not worth documenting?

* 174319: make.defaults needs to be parsed by things other than bash.
  Just how much of bash's syntax do we support?

* 174330: PMS currently bans interactivity except in pkg_config.

* 174335: Some ebuild use FEATURES. Can we get them to stop doing that,
  or do we have to force package managers to emulate it?

* 174536: Currently there's no way to tell whether you have a cat/pkg
  or a cat/pkg-ver, and in no place does anything have to do so. Do we
  want to introduce new restrictions so that people can do that?

* 175246: Portage sets EBUILD_PHASE=depend for the metadata source. Do
  we want to enforce this?

* 188449: The eight digit limit for version parts is still in. Do we
  want to keep it?

* 196561: PMS describes the ~ operator as working the way developers
  expect it to work, but Portage doesn't quite do that.

* 202631: PMS doesn't document profile.bashrc. Currently, Paludis
  ignores it because most of the code that ends up there is extremely
  Portage specific. Do we document profile.bashrc and make it much more
  constrained?

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2008-03-19 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 18:27 Ciaran McCreesh [this message]
2008-03-20  0:32 ` [gentoo-dev] Re: Remaining PMS todo list etc Ryan Hill
2008-03-20  3:45   ` Marius Mauch
2008-03-21  0:02     ` Ryan Hill
2008-03-21  7:54       ` Ciaran McCreesh
2008-03-21 18:17         ` Ryan Hill
2008-03-20  7:41   ` Ciaran McCreesh
2008-03-20  7:52     ` Christian Faulhammer
2008-03-20  7:55       ` Ciaran McCreesh
2008-03-21 11:47         ` Christian Faulhammer
2008-03-21 11:52           ` Ciaran McCreesh

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=20080319182717.69c0f975@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --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