Re: package manager thoughts

Gareth Buxton <[email protected]> 29 Jun 2003 02:58:57 +0100
Newsgroups gmane.linux.zynot.general
Message-ID <1056851937.24944.42.camel@localhost>
--===============63481733967143583==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-6VpFKZe/F3w+tyCa/RDk"


--=-6VpFKZe/F3w+tyCa/RDk
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


> Since we are in wait mode for the new updated documents,
> I wanted to see what everyone's opinions, thoughts were
> on some issues.
>=20
> 1. XML and its use as a package manager(pm)?

I think XML is fantastic if it is machine generated and machine read but
not ideal if you need to edit it manually.

> 2. What new features must the pm have?

Licensing control.
I like the idea of having licences implemented as packages. This way you
leverage the packaging system to implement licensing. You simply make a
given software-package dependent on a given license-package. When the
license-package dependency is met the user can be presented with an
intelligent response such as "Do you accept this license" or even in a
more commercial setting "Your license is out of date..." or even "Please
type in your credit-card details to purchase this license" - well that
kind of thing. Also you might want to vito software-packages if the
licence-package is not installed on the system. ZyNot development shops
for instance may want to ensure developers only work to 'in-house'
license-packages and maybe a couple of others like apache or LGPL. This
way they are protected by an automated system from developing against
libraries that would compromise their business model.

> 3. What would be nice features for the pm?

=46rom IRC roovis pointed out the dilemma of servicing a LAN. My thoughts
are that if the PM is going to have pluggable front end (there has been
discussion to this effect) then one route might be to develop a PM
Server front-end. So you could do /etc/init'd/pm start on one machine
and it could sit there listening for requests on the LAN and deliver
compiled packages for local installation. Once a day (configurable) it
could do an 'zymerge sync' to update. If the new PM dealt with cross
compilation this might also be a good thing for mobile devices and
heterogeneous environments servicing low powered machines.




--=-6VpFKZe/F3w+tyCa/RDk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

iD8DBQA+/kfhm0GAxmY3JIURAjLTAJ9JDl+xQBysIEhURQHG10flvePV+gCePuw2
3Hob3bm/REBsdEw5NODns1I=
=OCOr
-----END PGP SIGNATURE-----

--=-6VpFKZe/F3w+tyCa/RDk--


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

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

--===============63481733967143583==--