Re: Requirment Specification

--===============274208069224819==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-f3bdPTkSyj+i15DxbRhQ"


--=-f3bdPTkSyj+i15DxbRhQ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-09-05 at 06:00, Gareth Buxton wrote:
> Hi all
> We're trying to nail down all the requirements for the NEW version of
> the PackageManagementSystem after trawling through the Forums I have
> drafted a basic list of requirements. You can find it here:
>=20
> http://wiki.zynot.org/tiki/tiki-index.php?page=3DRequirementSpecification
>=20

Hi Gareth,

Thank you for compiling such a list, it gives a good start.

> Now is the time to make any final requests for functionality of the
> package manager. By this I mean the core system and not the user
> interface. It's also an opportunity for the powers that be (zach et al.)
> to accept/reject/prioritize ideas in this list.
>=20

Here are my list of features request which cannot be find or covered
partially in your list based on my use cases:

1. Staged build - Part of this has been covered in your list:=20
1.1 IMHO, these 5 stages are needed: Fetch, Source, Compile, Publish,
Install.
1.2 User should be able to stop at any stage.
1.3 User should be able to continue from any stage.

2. Non-root build on arbitrary working directory - I heard something
about "chroot" with Gentoo, but I am not sure if it is working well, at
least not for me.

3. Automatically use appropriate toolchain for specified target. User
can set preference in case multiple toolchains can be used to build for
that target.

4. Multiple derived packages can be produced by the same source package
by using different feature flag and architecture. When user wants to
install a derived package, the one with the right architecture and most
matched feature flag available in all configured  derived package
repository should be used.

5. Recipe repository/derived package repository are not necessary to be
together. A server can play any one of the role but not necessary two at
the same time.

> Also welcome would be contributions of use case scenarios which will be
> added to the document.

I was thinking to put following onto the tiki, but I cannot figure out
how to. :P

Scenario 1:

I usually want to install binary packages to save time. When I install a
binary package, the package with ost match "feature flag" exists on any
of
the feed I configured will be automatically selected.

Scenario 2:

I would like to join an open source project, so I want to build the
package from source code. I can then test the package. If there is
something I think need to be fixed, I would like to look at the source
code so that I can do some implementation, repeat the build/test
process. Once things are working as I expect, I can then create patches
for upstream maintainer.

Scenario 3:=20

The project can be compiled/tested on x86-linux platform, after I think
it is working, I want to cross-compile it for arm-linux platform. In
case there are portability issues, I can continue the development
process on either arm or x86 platform until all portablity issues are
addressed.

Regards,
Henry


--=-f3bdPTkSyj+i15DxbRhQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/XXmpLNaoAyBG0PURAp0dAJ9ynCSrOcyqT0P68jyjBAMGIlX+mQCfTrKU
+rdm7i6qljtJEMq7lkOsarE=
=WmCU
-----END PGP SIGNATURE-----

--=-f3bdPTkSyj+i15DxbRhQ--


--===============274208069224819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
zynaut mailing list
[email protected]
http://lists.zynot.org/mailman/listinfo/zynaut

--===============274208069224819==--