DragonFly BSD
DragonFly commits List (threaded) for 2005-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvs commit: src/share/examples/cvsup DragonFly-release1_4-supfile

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 29 Dec 2005 15:11:17 -0800 (PST)

:On Thu, December 29, 2005 12:48 pm, Matthew Dillon said:
:>   Added files:
:>     share/examples/cvsup DragonFly-release1_4-supfile
:>   Log:
:>   Add a cvsup example to track the 1.4 release.
:Would it be a good idea to add this to 1.2, also, since people can be
:upgrading from one to the other?
:This could allow us to indirectly control an upgrade path.  i.e. only
:supply new release supfiles for appropriate upgrades, so if there's an
:incompatibility between 1.2 and 2.2 (in theory), we don't supply a cvsup
:file.   This is assuming we are still using cvsup at that point.

    Well, there are some serious differences between 1.2 and 1.4.  All
    the libraries have gone through a major upgrade, the stat structure
    has changed size, and so on and so forth.  Program binaries will
    still run, of course, but the real problem is going to be the mixing
    and matching of libraries used by ports and packages.  It's just as
    well we are changing packaging systems at the same time :-).

    I see no problem with committing the 1.4 supfile to the 1.2 branch,
    go ahead and do it.

    We are going to have to move away from cvsup.  Requiring all of that
    modula infrastructure to run an 'essential' program has been a thorny
    issue for a long time and we have clearly hit the breaking point.  

    Your comments also imply that whatever new infrastructure we come up 
    with should be committed to 1.2 as well, and I definitely agree with 

					Matthew Dillon 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]