[Bioc-devel] exp. data, updates

Dan Tenenbaum dtenenba at fhcrc.org
Wed Jul 10 19:54:53 CEST 2013


On Wed, Jul 10, 2013 at 10:51 AM, Kasper Daniel Hansen
<kasperdanielhansen at gmail.com> wrote:
> This will help me branch code, but not objects with changed definitions.
>

Can you store two separate objects, one that's 2.12-compatible and the
other newer?

After the next release, when we stop building 2.12, this will become
unnecessary.

Dan


> Kasper
>
>
> On Wed, Jul 10, 2013 at 12:44 PM, Dan Tenenbaum <dtenenba at fhcrc.org> wrote:
>>
>> On Wed, Jul 10, 2013 at 7:05 AM, Kasper Daniel Hansen
>> <kasperdanielhansen at gmail.com> wrote:
>> > I have just changed the class definition for a core class in bsseq.  A
>> > supporting experiment data package, bsseqData, contains two objects of
>> > this
>> > core class and now it needs to be updated (specifically because the
>> > example() contains a command which prints the object and this printing
>> > now
>> > fails).
>> >
>> > I can update the bsseqData package, but do I mess with earlier releases
>> > when I do this? I am uncertain because the /data is stored in another
>> > repository. How should I handle this?
>> >
>>
>> The experiment data repository does not branch, so you could do something
>> like:
>>
>> DESCRIPTION:
>> Imports: BiocInstaller
>>
>> NAMESPACE:
>> import(BiocInstaller)
>>
>> Code:
>>
>> if (BiocInstaller:::BIOC_VERSION == "2.12")
>>    # do things the old way
>> else
>>   # do things the new way
>>
>> Dan
>>
>>
>>
>> > Best,
>> > Kasper
>> >
>> >         [[alternative HTML version deleted]]
>> >
>> > _______________________________________________
>> > Bioc-devel at r-project.org mailing list
>> > https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
>



More information about the Bioc-devel mailing list