RFC: Putting a "compatible" flag into the Control file and using it
tick at openmoko.com
Thu Aug 7 09:29:26 CEST 2008
I think it's a very good idea. It will solve a lot of problems for many
If we want to add this feature, I want to raise some questions first.
Do you have any idea that if we think distribution A can upgrade to B
but cannot updrade to C. How do we control this stuff.
Should this information put into Package file or .ipk/.opk file?
What if a repository does not provide any distribution info?
What if a ipk file is suit for multiple distributions?
On Sun, Aug 03, 2008 at 01:11:27PM +0200, Holger Freyther wrote:
> Hey Tick, Rob,
> I see constant breakage with people attempting an upgrade from
> org.openmoko.dev to org.openmoko.asu.stable. While such an upgrade might
> work, it might completely fail and break things. In my Opie past I even saw
> people "upgrading" to an eight year old Qtopia snapshot and messing up their
> system badly.
> I would propose the following and then do the patches:
> - Add "Compatible-Distribution" to the Control file and Packages index
> - Opkg gets an option for compatible distributions in "opkg.conf"
> - Opkg will only see packages from compatible distributions (on update)
> - Opkg will only install packages from compatible distributions
> - Opkg will ignore both on -force-any-distribution
> - Make the compatible distribution default
> I have seen a lot of breakage with such "upgrades" and even if it is obvious
> for us that this feed should not be used or might not be compatible, for many
> non developers they look perfectly fine. People knowing that asu.stable is
> compatible with a certain version of Poky or Angstrom, or want to install a
> debian package can use the -force-any-distribution to get their packages
> opkg-devel mailing list
> opkg-devel at lists.openmoko.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.openmoko.org/pipermail/opkg-devel/attachments/20080807/09f386fd/attachment.pgp
More information about the opkg-devel