I have finally gotten to start on building Trinity 3.5.13 for Arch linux.
I have built the dependencies plus kdelibs and kdebase.
I have it successfully running on a new i686 arch install and so far so good.
I am going to build the entire 3.5.13 release and want to make the packages available along the the PKGBUILD scripts.
I would like to build for both i686 and x86_64.
Is there a place I can upload my work to so others running arch can install it?
I have finally gotten to start on building Trinity 3.5.13 for Arch linux.
I have built the dependencies plus kdelibs and kdebase.
I have it successfully running on a new i686 arch install and so far so good.
I am going to build the entire 3.5.13 release and want to make the packages available along the the PKGBUILD scripts.
I would like to build for both i686 and x86_64.
Is there a place I can upload my work to so others running arch can install it?
Yes, the TDE project provides space for each distribution maintinance team to upload their packages. When you have a full set of binaries let me know and I'll give you further instructions.
Tim
On 12/06/2011 10:33 PM, Timothy Pearson wrote:
I have finally gotten to start on building Trinity 3.5.13 for Arch linux.
I have built the dependencies plus kdelibs and kdebase.
I have it successfully running on a new i686 arch install and so far so good.
I am going to build the entire 3.5.13 release and want to make the packages available along the the PKGBUILD scripts.
I would like to build for both i686 and x86_64.
Is there a place I can upload my work to so others running arch can install it?
Yes, the TDE project provides space for each distribution maintinance team to upload their packages. When you have a full set of binaries let me know and I'll give you further instructions.
Tim
Ok thanks
I will build all of the ones in the how to build document and then let you know.
2011/12/7 scrat baho-utot@columbus.rr.com:
On 12/06/2011 10:33 PM, Timothy Pearson wrote:
I have finally gotten to start on building Trinity 3.5.13 for Arch linux.
I have built the dependencies plus kdelibs and kdebase.
I have it successfully running on a new i686 arch install and so far so good.
I am going to build the entire 3.5.13 release and want to make the packages available along the the PKGBUILD scripts.
I would like to build for both i686 and x86_64.
Is there a place I can upload my work to so others running arch can install it?
Yes, the TDE project provides space for each distribution maintinance team to upload their packages. When you have a full set of binaries let me know and I'll give you further instructions.
Tim
Ok thanks
I will build all of the ones in the how to build document and then let you know.
Or upload them to aur.
On 8 December 2011 15:50, L0ner sh4dou sh4dou@gmail.com wrote:
2011/12/7 scrat baho-utot@columbus.rr.com:
On 12/06/2011 10:33 PM, Timothy Pearson wrote:
I have finally gotten to start on building Trinity 3.5.13 for Arch
linux.
I have built the dependencies plus kdelibs and kdebase.
I have it successfully running on a new i686 arch install and so far so good.
I am going to build the entire 3.5.13 release and want to make the packages available along the the PKGBUILD scripts.
I would like to build for both i686 and x86_64.
Is there a place I can upload my work to so others running arch can install it?
Yes, the TDE project provides space for each distribution maintinance
team
to upload their packages. When you have a full set of binaries let me know and I'll give you further instructions.
Tim
Ok thanks
I will build all of the ones in the how to build document and then let
you
know.
Or upload them to aur.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
You could upload them to our git tree. I also have PKGBUILDs ready Trinity that are available in the AUR and we can collaborate. I'd rather not duplicate our work.
On 12/08/2011 05:13 PM, Calvin Morrison wrote:
[putolin]
You could upload them to our git tree. I also have PKGBUILDs ready Trinity that are available in the AUR and we can collaborate. I'd rather not duplicate our work.
I could upload to git, but I will need help on how to do that. I haven't used git so I will need instruction to do so.
Collaboration would be great, no sense in everyone doing the same thing.
Along those lines may I suggest that a developer area is setup somewhere on a trinty servers that has the following info by package
1. Package name to be built 2. All the dependency packages used to build the package at this time. 3. The configure parameters etc. 4. How it was built.
Have a look at linux from scratch as an example.
This way all the various packagers will know what packages build, what doesn't currently build and how to go about building them. It would also help as it could be the "standard" build so as to correct errors on the various distro platforms. This way if someone is trying to build a package and it doesn't work you then know that it is platform problem and not with cmake or the source etc.
<snip>
Along those lines may I suggest that a developer area is setup somewhere on a trinty servers that has the following info by package
- Package name to be built
- All the dependency packages used to build the package at this time.
- The configure parameters etc.
How it was built.Have a look at linux from scratch as an example.
Good idea! The Wiki would be a good place for this document.
Tim
On 12/08/2011 06:03 PM, Timothy Pearson wrote:
<snip> > Along those lines may I suggest that a developer area is setup somewhere > on a trinty servers that has the following info by package > > 1. Package name to be built > 2. All the dependency packages used to build the package at this time. > 3. The configure parameters etc. > 4. How it was built. > > Have a look at linux from scratch as an example. Good idea! The Wiki would be a good place for this document.
Tim
Ok how to start it
Also there should be a section on the build environment ie gcc version autotools version etc.
On 12/08/2011 06:03 PM, Timothy Pearson wrote:
<snip> > Along those lines may I suggest that a developer area is setup > somewhere > on a trinty servers that has the following info by package > > 1. Package name to be built > 2. All the dependency packages used to build the package at this > time. > 3. The configure parameters etc. > 4. How it was built. > > Have a look at linux from scratch as an example. Good idea! The Wiki would be a good place for this document.
Tim
Ok how to start it
Also there should be a section on the build environment ie gcc version autotools version etc.
Try extending this Wiki page: http://trinitydesktop.org/wiki/bin/view/Developers/DistroSpecificBuilds
Tim
Le 09/12/2011 07:11, Timothy Pearson a écrit :
On 12/08/2011 06:03 PM, Timothy Pearson wrote:
<snip> > Along those lines may I suggest that a developer area is setup > somewhere > on a trinty servers that has the following info by package > > 1. Package name to be built > 2. All the dependency packages used to build the package at this > time. > 3. The configure parameters etc. > 4. How it was built. > > Have a look at linux from scratch as an example. Good idea! The Wiki would be a good place for this document.
Tim
Ok how to start it
Also there should be a section on the build environment ie gcc version autotools version etc.
Try extending this Wiki page: http://trinitydesktop.org/wiki/bin/view/Developers/DistroSpecificBuilds
I'm very interested by this idea and could contribute: I'm now building trinity on a CLFS system. I just created this page in the sandbox of the wiki that can be used as a first template: http://trinitydesktop.org/wiki/bin/view/Sandbox/TlfsLibart
On 8 December 2011 17:29, scrat baho-utot@columbus.rr.com wrote:
On 12/08/2011 05:13 PM, Calvin Morrison wrote:
[putolin]
You could upload them to our git tree. I also have PKGBUILDs ready Trinity that are available in the AUR and we can collaborate. I'd rather not duplicate our work.
I could upload to git, but I will need help on how to do that. I haven't used git so I will need instruction to do so.
Tim can we get him a Git account/ Help him whatever?
Collaboration would be great, no sense in everyone doing the same thing.
I suggest you check out my PKGBUILDs then :-)
-
Calvin Morrison -
L0ner sh4dou -
Laurent Dard -
scrat -
Timothy Pearson