You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2013/03/12 18:00:11 UTC
TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Arff, bad luck, it acts as submodule.
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Thursday, March 14, 2013 9:25 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
I maybe found another way to integrate TLF sub directories as part of
flex-sdk [1], still have to try it but sounds good.
-Fred
[1]
https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Wednesday, March 13, 2013 11:43 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
> BTW, are these separate "repos" as far as Git is concerned or something
> else?)
Humm..Can you reformulate that pls ? :P
The only way I see if we don't want to use links is to use submodules but to
use TLF as a submodule, it's root should be its sub directory textLayout so
is that what we want ?
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Tuesday, March 12, 2013 8:11 PM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
I think we don't want to use hard-links. And if submodules won't work, then
I think it is time to figure out how to cut releases by grabbing stuff from
different "repos". (BTW, are these separate "repos" as far as Git is
concerned or something else?)
At Adobe, TLF was developed in Perforce by another team and we took drops
for Flex. I'm sure we can do something similar.
On 3/12/13 11:37 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Submodules in Git are less flexible than svn:externals and less
> straightforward to use, you can plug an entire git repo as submodule but
> can't plug a sub-directory the a git repo as submodule. The problem with
> TLF
> is we need to plug the sub-directory called textLayout to the 3.0.33
> directory of our sdk repo, that's make submodules unusable.
>
> One way to go is to clone the TLF repo a part, make a hard link from the
> textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
> this directory at the sdk repo level, if we want to work on TLF, we can do
> it from the TLF repo itself.
>
> Note:
> - I've got this working and I finished to fill the .gitignore file.
> - On windows, there's a free software to manage soft/hard link, but it's
> one
> thing in more to do to setup the SDK that has to be explain in the readme.
>
> -Fred
>
> -----Message d'origine-----
> From: Alex Harui
> Sent: Tuesday, March 12, 2013 6:00 PM
> To: dev@flex.apache.org
> Subject: TLF Issue (was Re: SVN to Git migration in progress)
>
> Well, I'm still learning about Git, but it looks like we have to resolve
> the
> TLF svn:externals issue and it isn't clear that links in the file system
> are
> going to work on Windows and are the "correct" solution.
>
> Does anybody actually know the answer? Or do we just have to figure it
> out
> on our own.
>
> One thing I saw on the internet says that you can just pull from the other
> project if there aren't any conflicts with file names. Would that work?
>
> Were submodules and/or subtrees ruled out? It appeared from the Git
> manual
> that an update of the main project doesn't automatically update the
> submodules, so that will leave us open to making mistakes staying in sync.
>
> IMO, we should re-think why we had TLF as an svn:external. I think we
> just
> did it so the build scripts wouldn't have to change that much from the
> Adobe
> days, so we could find the source where we were used to seeing it.
>
> But looking not to far into the future, our releases may become a
> composition of stuff from the various Apache Flex "sub-projects". For
> example, the FlexJS stuff is compositing things from the old Flex SDK, the
> Falcon project and the ASJS project.
>
> So, given that we might have sync issues in Git even with submodules,
> maybe
> the answer is to rework the release scripts to composite from multiple
> projects?
>
> -Alex
>
>
>
> On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>> Still that :)
>>
>> I guess on windows I should find a way to to a hard link, right ?
>>
>> -Fred
>>
>> -----Message d'origine-----
>> From: Justin Mclean
>> Sent: Tuesday, March 12, 2013 11:26 AM
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>> Hi,
>>
>> Well the good news is other than the flex-sdk git repo compiles a usable
>> SDK
>> if you work around the TLF issue.
>>
>> Justin
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
I maybe found another way to integrate TLF sub directories as part of
flex-sdk [1], still have to try it but sounds good.
-Fred
[1]
https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Wednesday, March 13, 2013 11:43 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
> BTW, are these separate "repos" as far as Git is concerned or something
> else?)
Humm..Can you reformulate that pls ? :P
The only way I see if we don't want to use links is to use submodules but to
use TLF as a submodule, it's root should be its sub directory textLayout so
is that what we want ?
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Tuesday, March 12, 2013 8:11 PM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
I think we don't want to use hard-links. And if submodules won't work, then
I think it is time to figure out how to cut releases by grabbing stuff from
different "repos". (BTW, are these separate "repos" as far as Git is
concerned or something else?)
At Adobe, TLF was developed in Perforce by another team and we took drops
for Flex. I'm sure we can do something similar.
On 3/12/13 11:37 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Submodules in Git are less flexible than svn:externals and less
> straightforward to use, you can plug an entire git repo as submodule but
> can't plug a sub-directory the a git repo as submodule. The problem with
> TLF
> is we need to plug the sub-directory called textLayout to the 3.0.33
> directory of our sdk repo, that's make submodules unusable.
>
> One way to go is to clone the TLF repo a part, make a hard link from the
> textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
> this directory at the sdk repo level, if we want to work on TLF, we can do
> it from the TLF repo itself.
>
> Note:
> - I've got this working and I finished to fill the .gitignore file.
> - On windows, there's a free software to manage soft/hard link, but it's
> one
> thing in more to do to setup the SDK that has to be explain in the readme.
>
> -Fred
>
> -----Message d'origine-----
> From: Alex Harui
> Sent: Tuesday, March 12, 2013 6:00 PM
> To: dev@flex.apache.org
> Subject: TLF Issue (was Re: SVN to Git migration in progress)
>
> Well, I'm still learning about Git, but it looks like we have to resolve
> the
> TLF svn:externals issue and it isn't clear that links in the file system
> are
> going to work on Windows and are the "correct" solution.
>
> Does anybody actually know the answer? Or do we just have to figure it
> out
> on our own.
>
> One thing I saw on the internet says that you can just pull from the other
> project if there aren't any conflicts with file names. Would that work?
>
> Were submodules and/or subtrees ruled out? It appeared from the Git
> manual
> that an update of the main project doesn't automatically update the
> submodules, so that will leave us open to making mistakes staying in sync.
>
> IMO, we should re-think why we had TLF as an svn:external. I think we
> just
> did it so the build scripts wouldn't have to change that much from the
> Adobe
> days, so we could find the source where we were used to seeing it.
>
> But looking not to far into the future, our releases may become a
> composition of stuff from the various Apache Flex "sub-projects". For
> example, the FlexJS stuff is compositing things from the old Flex SDK, the
> Falcon project and the ASJS project.
>
> So, given that we might have sync issues in Git even with submodules,
> maybe
> the answer is to rework the release scripts to composite from multiple
> projects?
>
> -Alex
>
>
>
> On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>> Still that :)
>>
>> I guess on windows I should find a way to to a hard link, right ?
>>
>> -Fred
>>
>> -----Message d'origine-----
>> From: Justin Mclean
>> Sent: Tuesday, March 12, 2013 11:26 AM
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>> Hi,
>>
>> Well the good news is other than the flex-sdk git repo compiles a usable
>> SDK
>> if you work around the TLF issue.
>>
>> Justin
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
> BTW, are these separate "repos" as far as Git is concerned or something
> else?)
Humm..Can you reformulate that pls ? :P
The only way I see if we don't want to use links is to use submodules but to
use TLF as a submodule, it's root should be its sub directory textLayout so
is that what we want ?
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Tuesday, March 12, 2013 8:11 PM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
I think we don't want to use hard-links. And if submodules won't work, then
I think it is time to figure out how to cut releases by grabbing stuff from
different "repos". (BTW, are these separate "repos" as far as Git is
concerned or something else?)
At Adobe, TLF was developed in Perforce by another team and we took drops
for Flex. I'm sure we can do something similar.
On 3/12/13 11:37 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Submodules in Git are less flexible than svn:externals and less
> straightforward to use, you can plug an entire git repo as submodule but
> can't plug a sub-directory the a git repo as submodule. The problem with
> TLF
> is we need to plug the sub-directory called textLayout to the 3.0.33
> directory of our sdk repo, that's make submodules unusable.
>
> One way to go is to clone the TLF repo a part, make a hard link from the
> textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
> this directory at the sdk repo level, if we want to work on TLF, we can do
> it from the TLF repo itself.
>
> Note:
> - I've got this working and I finished to fill the .gitignore file.
> - On windows, there's a free software to manage soft/hard link, but it's
> one
> thing in more to do to setup the SDK that has to be explain in the readme.
>
> -Fred
>
> -----Message d'origine-----
> From: Alex Harui
> Sent: Tuesday, March 12, 2013 6:00 PM
> To: dev@flex.apache.org
> Subject: TLF Issue (was Re: SVN to Git migration in progress)
>
> Well, I'm still learning about Git, but it looks like we have to resolve
> the
> TLF svn:externals issue and it isn't clear that links in the file system
> are
> going to work on Windows and are the "correct" solution.
>
> Does anybody actually know the answer? Or do we just have to figure it
> out
> on our own.
>
> One thing I saw on the internet says that you can just pull from the other
> project if there aren't any conflicts with file names. Would that work?
>
> Were submodules and/or subtrees ruled out? It appeared from the Git
> manual
> that an update of the main project doesn't automatically update the
> submodules, so that will leave us open to making mistakes staying in sync.
>
> IMO, we should re-think why we had TLF as an svn:external. I think we
> just
> did it so the build scripts wouldn't have to change that much from the
> Adobe
> days, so we could find the source where we were used to seeing it.
>
> But looking not to far into the future, our releases may become a
> composition of stuff from the various Apache Flex "sub-projects". For
> example, the FlexJS stuff is compositing things from the old Flex SDK, the
> Falcon project and the ASJS project.
>
> So, given that we might have sync issues in Git even with submodules,
> maybe
> the answer is to rework the release scripts to composite from multiple
> projects?
>
> -Alex
>
>
>
> On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>> Still that :)
>>
>> I guess on windows I should find a way to to a hard link, right ?
>>
>> -Fred
>>
>> -----Message d'origine-----
>> From: Justin Mclean
>> Sent: Tuesday, March 12, 2013 11:26 AM
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>> Hi,
>>
>> Well the good news is other than the flex-sdk git repo compiles a usable
>> SDK
>> if you work around the TLF issue.
>>
>> Justin
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Alex Harui <ah...@adobe.com>.
Harbs is correct for a potential longer-term usage. It might be easier to
mimic the Flash dependencies it has in HTML/JS. The vast majority of the
code is computation of glyph positions.
For the short-term, since we're trying to emulate what you'll get in the
browser when running in Flash, we may use TLF to take html markup and
display it.
On 3/12/13 2:11 PM, "Harbs" <ha...@gmail.com> wrote:
> Eventually, there will need to be a comparable text engine for JS. Having a
> single interface for Flash TLF and Javascript TLF could be valuable.
>
> On Mar 12, 2013, at 10:33 PM, Om wrote:
>
>>>
>>> TLF has no Flex SDK dependencies so it is probably best kept separate and
>>> available for those not using the main Flex SDK. It might even get used by
>>> FlexJS users, for example.
>>>
>>>
>> How will FlexJS use it? Isnt TLF based on Flash Text Engine? I thought
>> the goal of FlexJS is to eliminate dependency on Flash?
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Harbs <ha...@gmail.com>.
Eventually, there will need to be a comparable text engine for JS. Having a single interface for Flash TLF and Javascript TLF could be valuable.
On Mar 12, 2013, at 10:33 PM, Om wrote:
>>
>> TLF has no Flex SDK dependencies so it is probably best kept separate and
>> available for those not using the main Flex SDK. It might even get used by
>> FlexJS users, for example.
>>
>>
> How will FlexJS use it? Isnt TLF based on Flash Text Engine? I thought
> the goal of FlexJS is to eliminate dependency on Flash?
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Om <bi...@gmail.com>.
On Tue, Mar 12, 2013 at 1:18 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 3/12/13 1:03 PM, "Om" <bi...@gmail.com> wrote:
>
> > On Tue, Mar 12, 2013 at 12:58 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >>
> >>
> >>
> >> On 3/12/13 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
> >>
> >>> Why is TLF a separate repro at all? Why isn't it just part of the sdk
> >> repro?
> >>>
> >> Might be possible, but TLF came late and had its own set of branches
> and no
> >> SVN history so we kept it external.
> >>
> >>
> > I think we should just copy the TLF project into the appropriate
> directory
> > path under the sdk. I dont see any value keeping it as separate top
> level
> > project.
> >
> > And this is probably the best time to do this.
> >
> I think it is best if we learn to deal with "external" repos. When we make
> Falcon the default compiler, we won't copy it into SDK will we? And
> BlazeDS, and Squiggly, etc.
>
>
I agree with the general principle about having to deal with externals.
But I am not very sure what plans we have for TLF though.
> TLF has no Flex SDK dependencies so it is probably best kept separate and
> available for those not using the main Flex SDK. It might even get used by
> FlexJS users, for example.
>
>
How will FlexJS use it? Isnt TLF based on Flash Text Engine? I thought
the goal of FlexJS is to eliminate dependency on Flash?
Thanks,
Om
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I think we should just copy the TLF project into the appropriate directory
> path under the sdk. I dont see any value keeping it as separate top level
> project.
-1 to this the FLEX SDK uses a subdirectory of TLF not the root.
Justin
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Alex Harui <ah...@adobe.com>.
On 3/12/13 1:03 PM, "Om" <bi...@gmail.com> wrote:
> On Tue, Mar 12, 2013 at 12:58 PM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>>
>> On 3/12/13 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>>
>>> Why is TLF a separate repro at all? Why isn't it just part of the sdk
>> repro?
>>>
>> Might be possible, but TLF came late and had its own set of branches and no
>> SVN history so we kept it external.
>>
>>
> I think we should just copy the TLF project into the appropriate directory
> path under the sdk. I dont see any value keeping it as separate top level
> project.
>
> And this is probably the best time to do this.
>
I think it is best if we learn to deal with "external" repos. When we make
Falcon the default compiler, we won't copy it into SDK will we? And
BlazeDS, and Squiggly, etc.
TLF has no Flex SDK dependencies so it is probably best kept separate and
available for those not using the main Flex SDK. It might even get used by
FlexJS users, for example.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Om <bi...@gmail.com>.
On Tue, Mar 12, 2013 at 12:58 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 3/12/13 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>
> > Why is TLF a separate repro at all? Why isn't it just part of the sdk
> repro?
> >
> Might be possible, but TLF came late and had its own set of branches and no
> SVN history so we kept it external.
>
>
I think we should just copy the TLF project into the appropriate directory
path under the sdk. I dont see any value keeping it as separate top level
project.
And this is probably the best time to do this.
Thanks,
Om
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Alex Harui <ah...@adobe.com>.
On 3/12/13 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
> Why is TLF a separate repro at all? Why isn't it just part of the sdk repro?
>
Might be possible, but TLF came late and had its own set of branches and no
SVN history so we kept it external.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Harbs <ha...@gmail.com>.
Why is TLF a separate repro at all? Why isn't it just part of the sdk repro?
On Mar 12, 2013, at 9:11 PM, Alex Harui wrote:
> I think we don't want to use hard-links. And if submodules won't work, then
> I think it is time to figure out how to cut releases by grabbing stuff from
> different "repos". (BTW, are these separate "repos" as far as Git is
> concerned or something else?)
>
> At Adobe, TLF was developed in Perforce by another team and we took drops
> for Flex. I'm sure we can do something similar.
>
>
> On 3/12/13 11:37 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>> Submodules in Git are less flexible than svn:externals and less
>> straightforward to use, you can plug an entire git repo as submodule but
>> can't plug a sub-directory the a git repo as submodule. The problem with TLF
>> is we need to plug the sub-directory called textLayout to the 3.0.33
>> directory of our sdk repo, that's make submodules unusable.
>>
>> One way to go is to clone the TLF repo a part, make a hard link from the
>> textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
>> this directory at the sdk repo level, if we want to work on TLF, we can do
>> it from the TLF repo itself.
>>
>> Note:
>> - I've got this working and I finished to fill the .gitignore file.
>> - On windows, there's a free software to manage soft/hard link, but it's one
>> thing in more to do to setup the SDK that has to be explain in the readme.
>>
>> -Fred
>>
>> -----Message d'origine-----
>> From: Alex Harui
>> Sent: Tuesday, March 12, 2013 6:00 PM
>> To: dev@flex.apache.org
>> Subject: TLF Issue (was Re: SVN to Git migration in progress)
>>
>> Well, I'm still learning about Git, but it looks like we have to resolve the
>> TLF svn:externals issue and it isn't clear that links in the file system are
>> going to work on Windows and are the "correct" solution.
>>
>> Does anybody actually know the answer? Or do we just have to figure it out
>> on our own.
>>
>> One thing I saw on the internet says that you can just pull from the other
>> project if there aren't any conflicts with file names. Would that work?
>>
>> Were submodules and/or subtrees ruled out? It appeared from the Git manual
>> that an update of the main project doesn't automatically update the
>> submodules, so that will leave us open to making mistakes staying in sync.
>>
>> IMO, we should re-think why we had TLF as an svn:external. I think we just
>> did it so the build scripts wouldn't have to change that much from the Adobe
>> days, so we could find the source where we were used to seeing it.
>>
>> But looking not to far into the future, our releases may become a
>> composition of stuff from the various Apache Flex "sub-projects". For
>> example, the FlexJS stuff is compositing things from the old Flex SDK, the
>> Falcon project and the ASJS project.
>>
>> So, given that we might have sync issues in Git even with submodules, maybe
>> the answer is to rework the release scripts to composite from multiple
>> projects?
>>
>> -Alex
>>
>>
>>
>> On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>>
>>> Still that :)
>>>
>>> I guess on windows I should find a way to to a hard link, right ?
>>>
>>> -Fred
>>>
>>> -----Message d'origine-----
>>> From: Justin Mclean
>>> Sent: Tuesday, March 12, 2013 11:26 AM
>>> To: dev@flex.apache.org
>>> Subject: Re: SVN to Git migration in progress
>>>
>>> Hi,
>>>
>>> Well the good news is other than the flex-sdk git repo compiles a usable
>>> SDK
>>> if you work around the TLF issue.
>>>
>>> Justin
>>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Alex Harui <ah...@adobe.com>.
I think we don't want to use hard-links. And if submodules won't work, then
I think it is time to figure out how to cut releases by grabbing stuff from
different "repos". (BTW, are these separate "repos" as far as Git is
concerned or something else?)
At Adobe, TLF was developed in Perforce by another team and we took drops
for Flex. I'm sure we can do something similar.
On 3/12/13 11:37 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Submodules in Git are less flexible than svn:externals and less
> straightforward to use, you can plug an entire git repo as submodule but
> can't plug a sub-directory the a git repo as submodule. The problem with TLF
> is we need to plug the sub-directory called textLayout to the 3.0.33
> directory of our sdk repo, that's make submodules unusable.
>
> One way to go is to clone the TLF repo a part, make a hard link from the
> textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
> this directory at the sdk repo level, if we want to work on TLF, we can do
> it from the TLF repo itself.
>
> Note:
> - I've got this working and I finished to fill the .gitignore file.
> - On windows, there's a free software to manage soft/hard link, but it's one
> thing in more to do to setup the SDK that has to be explain in the readme.
>
> -Fred
>
> -----Message d'origine-----
> From: Alex Harui
> Sent: Tuesday, March 12, 2013 6:00 PM
> To: dev@flex.apache.org
> Subject: TLF Issue (was Re: SVN to Git migration in progress)
>
> Well, I'm still learning about Git, but it looks like we have to resolve the
> TLF svn:externals issue and it isn't clear that links in the file system are
> going to work on Windows and are the "correct" solution.
>
> Does anybody actually know the answer? Or do we just have to figure it out
> on our own.
>
> One thing I saw on the internet says that you can just pull from the other
> project if there aren't any conflicts with file names. Would that work?
>
> Were submodules and/or subtrees ruled out? It appeared from the Git manual
> that an update of the main project doesn't automatically update the
> submodules, so that will leave us open to making mistakes staying in sync.
>
> IMO, we should re-think why we had TLF as an svn:external. I think we just
> did it so the build scripts wouldn't have to change that much from the Adobe
> days, so we could find the source where we were used to seeing it.
>
> But looking not to far into the future, our releases may become a
> composition of stuff from the various Apache Flex "sub-projects". For
> example, the FlexJS stuff is compositing things from the old Flex SDK, the
> Falcon project and the ASJS project.
>
> So, given that we might have sync issues in Git even with submodules, maybe
> the answer is to rework the release scripts to composite from multiple
> projects?
>
> -Alex
>
>
>
> On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>> Still that :)
>>
>> I guess on windows I should find a way to to a hard link, right ?
>>
>> -Fred
>>
>> -----Message d'origine-----
>> From: Justin Mclean
>> Sent: Tuesday, March 12, 2013 11:26 AM
>> To: dev@flex.apache.org
>> Subject: Re: SVN to Git migration in progress
>>
>> Hi,
>>
>> Well the good news is other than the flex-sdk git repo compiles a usable
>> SDK
>> if you work around the TLF issue.
>>
>> Justin
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Submodules in Git are less flexible than svn:externals and less
straightforward to use, you can plug an entire git repo as submodule but
can't plug a sub-directory the a git repo as submodule. The problem with TLF
is we need to plug the sub-directory called textLayout to the 3.0.33
directory of our sdk repo, that's make submodules unusable.
One way to go is to clone the TLF repo a part, make a hard link from the
textLayout directory to a new 3.0.33 directory in the sdk repo, gitignore
this directory at the sdk repo level, if we want to work on TLF, we can do
it from the TLF repo itself.
Note:
- I've got this working and I finished to fill the .gitignore file.
- On windows, there's a free software to manage soft/hard link, but it's one
thing in more to do to setup the SDK that has to be explain in the readme.
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Tuesday, March 12, 2013 6:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable
> SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Oh more like a "MKLINK /D /H LinkFolder TargetFolder".
Thanks for the information.
-Mark
-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Sent: Thursday, March 14, 2013 6:37 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
No I used Symbolic Links for windows [1]
You create a junction from flex-tlf/textLayout to
project/framework/textLayout/3.0.33
You'll have to rename the freshly created textLayout under junction folder
(under project/framework/textLayout/) to 3.0.33
-Fred
[1]
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
No I used Symbolic Links for windows [1]
You create a junction from flex-tlf/textLayout to
project/framework/textLayout/3.0.33
You'll have to rename the freshly created textLayout under junction folder
(under project/framework/textLayout/) to 3.0.33
-Fred
[1]
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
-----Message d'origine-----
From: Kessler CTR Mark J
Sent: Thursday, March 14, 2013 11:20 AM
To: dev@flex.apache.org
Subject: RE: TLF Issue (was Re: SVN to Git migration in progress)
Did you use the " fsutil hardlink create NewFilename ExistingFilename" ?
-Mark
-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Sent: Thursday, March 14, 2013 6:01 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
yep, the only way I found to resolve this at the moment was to create a hard
link to textLayout sub directory of the flex-tlf git project.
-Fred
-----Message d'origine-----
From: Kessler CTR Mark J
Sent: Thursday, March 14, 2013 10:53 AM
To: dev@flex.apache.org
Subject: RE: TLF Issue (was Re: SVN to Git migration in progress)
Would this be why I got a failed build on the text layout portion of the git
develop branch?
compile:
[compc] Loading configuration file
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-
config.xml(58): Error: unable to open
'D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout/3.0.33/manifest.xml'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
D:\Development\Flex\Flex-SDK\build.xml:361: The following error occurred
while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:91: The following error
occurred while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:387: The following error
occur red while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\build.xml:179:
compc task failed.
Total time: 1 minute 3 seconds
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, March 12, 2013 1:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable
> SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Did you use the " fsutil hardlink create NewFilename ExistingFilename" ?
-Mark
-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Sent: Thursday, March 14, 2013 6:01 AM
To: dev@flex.apache.org
Subject: Re: TLF Issue (was Re: SVN to Git migration in progress)
yep, the only way I found to resolve this at the moment was to create a hard
link to textLayout sub directory of the flex-tlf git project.
-Fred
-----Message d'origine-----
From: Kessler CTR Mark J
Sent: Thursday, March 14, 2013 10:53 AM
To: dev@flex.apache.org
Subject: RE: TLF Issue (was Re: SVN to Git migration in progress)
Would this be why I got a failed build on the text layout portion of the git
develop branch?
compile:
[compc] Loading configuration file
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-
config.xml(58): Error: unable to open
'D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout/3.0.33/manifest.xml'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
D:\Development\Flex\Flex-SDK\build.xml:361: The following error occurred
while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:91: The following error
occurred while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:387: The following error
occur red while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\build.xml:179:
compc task failed.
Total time: 1 minute 3 seconds
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, March 12, 2013 1:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable
> SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Frédéric THOMAS <we...@hotmail.com>.
yep, the only way I found to resolve this at the moment was to create a hard
link to textLayout sub directory of the flex-tlf git project.
-Fred
-----Message d'origine-----
From: Kessler CTR Mark J
Sent: Thursday, March 14, 2013 10:53 AM
To: dev@flex.apache.org
Subject: RE: TLF Issue (was Re: SVN to Git migration in progress)
Would this be why I got a failed build on the text layout portion of the git
develop branch?
compile:
[compc] Loading configuration file
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-
config.xml(58): Error: unable to open
'D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout/3.0.33/manifest.xml'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
D:\Development\Flex\Flex-SDK\build.xml:361: The following error occurred
while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:91: The following error
occurred while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:387: The following error
occur red while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\build.xml:179:
compc task failed.
Total time: 1 minute 3 seconds
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, March 12, 2013 1:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable
> SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: TLF Issue (was Re: SVN to Git migration in progress)
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Would this be why I got a failed build on the text layout portion of the git develop branch?
compile:
[compc] Loading configuration file D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc] D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-
config.xml(58): Error: unable to open 'D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout/3.0.33/manifest.xml'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
D:\Development\Flex\Flex-SDK\build.xml:361: The following error occurred while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:91: The following error occurred while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:387: The following error occur red while executing this line:
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\build.xml:179: compc task failed.
Total time: 1 minute 3 seconds
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, March 12, 2013 1:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)
Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.
Does anybody actually know the answer? Or do we just have to figure it out
on our own.
One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names. Would that work?
Were submodules and/or subtrees ruled out? It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.
IMO, we should re-think why we had TLF as an svn:external. I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.
But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects". For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.
So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple
projects?
-Alex
On 3/12/13 3:59 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Still that :)
>
> I guess on windows I should find a way to to a hard link, right ?
>
> -Fred
>
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
>
> Hi,
>
> Well the good news is other than the flex-sdk git repo compiles a usable SDK
> if you work around the TLF issue.
>
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui