Barry, Reading the quote from the manual reminded me now. Previously, i had patch files put in target/$target/pkg_$pkg.patch and also target/$target/package/$pkg/<patchfile>.patch.
It worked out fine for me, except that patches are applied mutually from the target and repository. I had a problem when I only wanted the patches from the target to be applied when there was a desc file overlay. For example, in a target, i may have a package linux with a desc file defining and locking to kernel 2.6.31 and some driver update patches I created that are specific to linux-2.6.31. With t2-sde-9.0, it would apply all patches from the repository, and those patches may completely be for a different kernel version, and on top of that, it would apply patches in the target for kernel 2.6.31. It was not possible to maintain a specific package locally and having the repository updating from the svn server for new package update changes. Therefore, i created the patch to be able to lock in a specific package, including its version and associated patches, to a target; and it had to be immune from package updates of SDE's repository. Moreover, one can add private 3rd party packages in a target and not having to worry about maintaining it (ie. having to define it in the repository and upload to the repository). A perfect example would be a distribution OS installer for a target, in this case, a target is like a linux distro. On Wed, Jul 3, 2013 at 10:08 PM, Barry Kauler <[email protected]> wrote: > Ok, next morning! > > From the manual, the feature I am using is supported from v7.0, > quoting from manual: > > ---------------------------- > Since this facility does not allow to alter the actual version and > download location of the package, since T2 version 7.0 it is > furthermore possible to completely overlay and inherit packages. This > is usually useful if an architecture patch is only available for a > special GCC or Linux kernel release, or maybe even so new to be a > snapshot release. Also special requirements like an older PHP, MySQL, > Wine, etc. version due to incompatible features in the current T2 > version might be a reason to force a specific known good or certified > version in a target. > > Defining a target specific version is identical to creating a normal > T2 package, but just inside a target's directory named > target/$targetname/package/$pkg, like > target/$targetname/package/apache/. Inside this directory the normal > files, such as $pkg.desc, $pkg.conf, and patches can be placed. The > exact semantic behaviour is: > > The .desc inherits everything from the main-tree package/, so it > is enough to just have [V] and [D] in this overlay .desc. > > The .conf is completely inherited by default from the main-tree > package/ until another or empty one is create it in this overlay > package. To inherit parts the original one can manually be sourced > (source or . operator) > -------------------------------------------- > > For example, I have overlaid 'cups', using an older version, 1.4.8 > instead of 1.6.2. > I see that config/wary6/packages still shows version as 1.6.2, though, > it does build 1.4.8. I presume also that 'packages' file is where T2 > gets it's priority information, which might explain why it ignores a > "[P]" override in a .desc file. > > I can create a .desc file with just one line "[P] ...." and it is > ignored. But, "[V]" and "[D]" overrides are recognised. > > Regards, > Barry Kauler > > > > On 7/4/13, Barry Kauler <[email protected]> wrote: > > On 7/4/13, Toan Pham <[email protected]> wrote: > >>> This time I decided to do it properly. From the manual instructions, I > >>> created ("wary6" is my target-name): > >>> > >> > >> From the manual instructions? Really? I had to modify SDE-9.0-trunk > >> for > >> to get this feature. > > > > Yes, read: > > file:///mnt/sda10/t2/t2-book.html > > > > I am using T2 source from svn yesterday. > > > > It does partly work. It works for [V] and [D], but it seems not for > > [P], which is weird. > > > > Anyway, it's 2am here and I'm burnt out, going to bed. > > > > > >> > >>> > >>> target/wary6/package/udev/udev.desc > >>> > >>> ...with this change: > >>> > >>> #[P] X -----5---9 127.000 > >>> [P] X -1---5---9 102.030 > >>> > >>> To be absolutely sure this change got picked up, I reran the Config, > >>> then Build-Target, but it is ignoring my override, still using the > >>> original. > >>> > >> > >> > >> Please look at t2 mailing list on 8/24/12 > >> There was a patch that i sent to the list that would allow you to have > >> package overlay settings in each target. It is exactly what you're > >> trying > >> to do. I have been using this method since. > >> > >> > >> Barry, this is a reference to the patch email in case if you can not > find > >> it: Let me know if the patch work for you. > >> > >> > --------------------------------------------------------------------------------------------------------------------- > >> > >> Rene, > >> > >> > >> The included patch will support building of packages from the target > >> only, > >> and also overlaying old package config from the target if a description > >> file is found on the target folder. Please test it and make sure it > does > >> not break anything. I tested it, and it did not impact the normal build > >> process on my system. > >> > >> > >> thank you.[image: > >> target_package_config.9.0sde.patch]< > https://mail.google.com/mail/u/0/?ui=2&ik=87dafe7029&view=att&th=13958f2f2c7322b2&attid=0.1&disp=safe&realattid=f_h69ciitd0&zw > > > >> *target_package_config.9.0sde.patch* > >> 3K > >> Download< > https://mail.google.com/mail/u/0/?ui=2&ik=87dafe7029&view=att&th=13958f2f2c7322b2&attid=0.1&disp=safe&realattid=f_h69ciitd0&zw > > > >> > > >
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
