SlackBuild sync between 7.0 and 7.1 branch??

Issue #35 wontfix
hata_ph created an issue

I notice any changes that you do in 7.0 branch will not take effect on 7.1 branch. Is there an easy to do so beside manually update the 7.1 SB?

Comments (3)

  1. Moises Henriquez

    This is actually done on purpose, and a good thing. I'll explain.

    Git allows us to have 2 (or more) different versions of the same SB. One in each branch. We can say that this feature in git is allowing us to keep all of our SB's in one place and still distinguish what goes where.

    Take for instance the 7.0 and 7.1 releases. The configure triplet changed on the SB's from 7.0 to 7.1. The SB's have been patched, but any new SB's for 7.1 need to be generated from sbbuilder from 7.1 so that the correct CONFIGURE TRIPLET is used.

    Another use case: The dependencies needed for an application to build on 7.0 are different from 7.1. Having different versions of the SB allows us to handle this properly.

    and one more use case for this... 7.0 reaches END OF LIFE, so no more updates on it. We can continue to update the SB for other 7.1 and future, without having to build (and fail) 7.0 packages.

    There are proble more advantages, but I think these prove the point I'm trying to make.

    Git branching allows us to manage these changes between releases. You can read more about git branching here http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging

  2. Log in to comment