Thread: [SEToolkit-developer] Fwd: Some questions regarding install locations
Brought to you by:
dmichelsen
Menu
▾
▴
setoolkit-developer
|
From: Dagobert M. <da...@ba...> - 2007-06-13 13:22:37
|
-- Dagobert Michelsen (Leiter IT) Baltic Online Computer GmbH Firmensitz: Alter Markt 1-2, 24103 Kiel, Telefon: +49 431 54003-0 Geschäftsführer: Erik Cickovskis, Amtsgericht Kiel, HRB 3756 "Of course computer servers don't need thrust, since they generally don't go anywhere." -- Comment in TR on new HP server turbine fans --- the forwarded message follows --- |
|
From: Alex K. <ale...@gm...> - 2007-06-13 14:14:07
|
On 13/06/07, Dagobert Michelsen <da...@ba...> wrote:
> Hi Alex,
>
> I managed to build a package for blastwave, however the structure
> is quite different:
> - the include files are in $prefix/share/se/include instead of
> $prefix/include
> - the examples are in $prefix/share/se/examples instead of
> $prefix/examples
So, I that matches the layout you get with a simple --prefix? I think
we had a conversation in the past where we talked about changing some
of that - I'm afraid I've been off on a number of other things, so
I've somewhat forgotten where we were...
> - the se-binary is now in $prefix/libexec/se.`isainfo -k`
> - $prefix/bin/se is now the script in $workdir/bin/se
If we put the binaries into sparcv7/sparcv9/i86/amd64 subdirectories,
we could use a simple isaexec wrapper (this is what I've used for our
internal stuff for several years), assuming we didn't want to deliver
sparc/x86 within the same package:
#include <stdlib.h>
#include <unistd.h>
int
main(int argc, char *argv[], char *envp[])
{
return isaexec(getexecname(), argv, envp);
}
I was never very happy with all the voodoo which the se script did
with respect to picking up stuff magically.
> I think it would be a good idea to use these new pathes and
> provide links in the package from the old locations.
>
I agree on the new paths - seems like the right time to make setoolkit
more like everything else (and for blastwave so it fits properly into
the /opt/csw tree).
Is one approach to deliver a RICHPse package which is just a symlink
farm across into CSWsetoolkit (assuming that's what you're naming the
package - I'm just guessing here)?
--
Alex Kiernan
|
|
From: Dagobert M. <da...@ba...> - 2007-06-14 07:22:32
|
Hi Jon, Am 13.06.2007 um 16:40 schrieb Tankersley, Jon: > For my 2 pfennig's worth... Since we have Euros now the Pfennig is a bit outdated ;-) > Any solution for packaging I will probably ignore and rebuild a > complete > all binary Sun pkg file. Ok, so I'll prepare a tgz with the sources for download too. > I need to be able to just point people at one > place and not make them think about it. As long as the underlying > structure will support all three to be simultaneously present and work > properly with the appropriate underlying hardware in place, I'll be > fine. Of course all packages should contain similar content (with more or less examples and contributed stuff). > I have to live with other guidelines for deployment and I'm not > sure I can push 'blastwave'. No need to do. This is just one more option for people who already get their package from blastwave. > I don't know if you'd be interested in my 'repackaging' scripts or > not. Sure, maybe there's a hinch I can adopt. Best regards -- Dagobert -- "Of course computer servers don't need thrust, since they generally don't go anywhere." -- Comment in TR on new HP server turbine fans |
|
From: Alex K. <ale...@gm...> - 2007-06-14 08:07:44
|
On 14/06/07, Dagobert Michelsen <da...@ba...> wrote: > > Any solution for packaging I will probably ignore and rebuild a > > complete > > all binary Sun pkg file. > > Ok, so I'll prepare a tgz with the sources for download too. > One thing to watch when doing `make dist', if you don't make se-parser.c first it won't get included in the bundle - perhaps we should force dist to depend on $(BUILT_SOURCES)? -- Alex Kiernan |
|
From: Dagobert M. <da...@ba...> - 2007-06-14 08:20:17
|
Hi Alex, Am 14.06.2007 um 10:07 schrieb Alex Kiernan: > On 14/06/07, Dagobert Michelsen <da...@ba...> wrote: >> > Any solution for packaging I will probably ignore and rebuild a >> > complete >> > all binary Sun pkg file. >> >> Ok, so I'll prepare a tgz with the sources for download too. > > One thing to watch when doing `make dist', if you don't make > se-parser.c first it won't get included in the bundle - perhaps we > should force dist to depend on $(BUILT_SOURCES)? Yes. And there are some other files which should be included like pkg/. I was thinking of a checkout, autoreconf, remove .svn-stuff and tar that. If it is easy to include those files in Makefile.am for tardist without getting them installed that would be even bet- ter. Best regards -- Dago -- "Of course computer servers don't need thrust, since they generally don't go anywhere." -- Comment in TR on new HP server turbine fans |
|
From: Alex K. <ale...@gm...> - 2007-06-14 11:54:19
|
On 14/06/07, Dagobert Michelsen <da...@ba...> wrote: > Hi Alex, > > Am 14.06.2007 um 10:07 schrieb Alex Kiernan: > > On 14/06/07, Dagobert Michelsen <da...@ba...> wrote: > >> > Any solution for packaging I will probably ignore and rebuild a > >> > complete > >> > all binary Sun pkg file. > >> > >> Ok, so I'll prepare a tgz with the sources for download too. > > > > One thing to watch when doing `make dist', if you don't make > > se-parser.c first it won't get included in the bundle - perhaps we > > should force dist to depend on $(BUILT_SOURCES)? > > Yes. And there are some other files which should be included like > pkg/. I was thinking of a checkout, autoreconf, remove .svn-stuff > and tar that. If it is easy to include those files in Makefile.am > for tardist without getting them installed that would be even bet- > ter. > ./configure && make dist /ought/ to build a tarball which includes everything which goes into a distribution. make dist-check will tell you if there are things which are needed which aren't there. If it doesn't its a bug. -- Alex Kiernan |
Thanks for helping keep SourceForge clean.
X