search

DragonFlyBSD / DPorts

The dedicated application build system for DragonFly BSD
Other
89 stars 44 forks source link

Dports needs an UPDATING file just like FreeBSD ports has. #88

Closed davshao closed 10 years ago

davshao commented 10 years ago

Dports needs an UPDATING file just like FreeBSD ports has. For example, when the next round of updates from FreeBSD ports are applied, there is a note in FreeBSD ports UPDATING:

20140219: AFFECTS: users of textproc/docbook* AUTHOR: mat@FreeBSD.org

The textproc/docbook-* ports have been consolidated into two ports textproc/docbook-sgml and textproc/docbook-xml.

Before upgrading you should force the removal of the existing ports, they will conflict with the new ones.

pkg users can run:

pkg delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\*

the other users can run:

pkg_delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\*
jrmarino commented 10 years ago

I'll think about it. At some point "pkg" should be able to handle a case like this automatically, but I don't know how far off that is (3 months? 12 months?).

I didn't wanted "MOVED" either but in the end I had to port a truncated version of it (MOVED goes back more than 7 years, but I only bring in Jan 2013 on). Maybe something similar for UPDATING could/should be done.

davshao commented 10 years ago

The recently closed "Intel graphics machines G45 and HD Graphics "has no monitor section"" #87 shows another reason why a custom /usr/dports/UPDATING might be necessary for DragonFly. Unless someone affected knew to look in the closed bug reports, that person would be unaware of having to reinstall x11-drivers/xf86-video-intel on an affected machine, especially if DragonFly retains the ports versions from FreeBSD so that it would not be possible for portmaster to know that xf86-video-intel should be upgraded.

fupjack commented 10 years ago

This may be more of a question for the makers of pkg, but: it would be interesting to have pkg, when you issue an upgrade command, fetch an UPDATING text page from whatever mirror, with a list of issues relevant since the next release, and feed it into less, so that the upgrading person can review it.

The issues could be tagged to the affected ports, so that it only displays notes relevant to the upgrade - but that's adding another layer of complexity that isn't supported by the underlying ports system right now.

jrmarino commented 10 years ago

Okay, UPDATING is now in place. It only contains one year's worth of entries. Anything older than 1 year is truncated each time the dports are regenerated.