Menu
▾
▴
linuxcoe-devel
|
From: Bruno C. <Bru...@hp...> - 2007-03-09 10:20:53
|
Hello, It seems that the systemdesigner part of LinuxCOE will be difficult to package. 1/ it seems that the planed directory organisation is under a single main dir (I choose /usr/local/systemdesigner) where the LSB/FHS integration would rather imply using /usr, /var/log, /etc, ... We will have to pass a lot of parameters to configure in order to achieve that, I guess. 2/ The Apache conf file is not installed by the make install proceudre (under the service dir) and I think it's a bug. 3/ Is there a bugzilla somewhere we could use ? 4/ There should also be an easy way to download files compared to CVS (again for some tools helping to build packages it's easier). That's all for now, but I may come back with further questions :-) Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org |
|
From: Lee M. <lee...@hp...> - 2007-03-09 11:40:51
|
Hi Bruno, My comments in-line: Bruno Cornec wrote: > Hello, > > It seems that the systemdesigner part of LinuxCOE will be difficult to > package. > > 1/ it seems that the planed directory organisation is under a single > main dir (I choose /usr/local/systemdesigner) where the LSB/FHS > integration would rather imply using /usr, /var/log, /etc, ... > We will have to pass a lot of parameters to configure in order to achieve > that, I guess. > When we originally decide on filesystem locations, we went with: /opt/package - Static package objects /etc/opt/package - Host specific configuration (optional) /var/opt/package - Volatile data - namely profiles and logs Bryan and I (mostly Bryan :) parameterized all pathnames with @prefix@ in the code, so it's relatively easy to relocate the package and all its components to a different path. The /etc tree is completely optional, but useful as it allows you to protect any changes between updates (it's a mirror of what's in /opt/package and takes precedence for config/data directives). I'm happy changing this if it makes sense. > 2/ The Apache conf file is not installed by the make install proceudre > (under the service dir) and I think it's a bug. > > This is a function of 'make integrate', which will also update sudoers if you require that functionality, which is mostly for older distros where I need to loopmount initrd to make changes. It's separate from 'make install' as it's something you only do once. > 3/ Is there a bugzilla somewhere we could use ? > There's the standard bug-tracker provided by sf.net: http://sourceforge.net/tracker/?group_id=144250&atid=758199 We should all start using it. > 4/ There should also be an easy way to download files compared to CVS > (again for some tools helping to build packages it's easier). > In the past we've included 'virgin' boot images for the majority of the distributions we support. While this was convenient for users, it put us at odds with sourceforge's disk quotes. Chris Slater kindly hosts 'tarball' snapshots of System Designer at installinux: http://www.instalinux.com/LinuxCOE/snapshot/ We'll be removing these images and including instructions on how to create your own (and perhaps hosting tarballs of just the images remotely) to decrease our disk space usage on sf.net and allow true build releases on sf.net soon. > That's all for now, but I may come back with further questions :-) > Bruno. > Hope that helps, Bryan will elaborate further I'm sure! Best Regards, Lee |
|
From: Louis B. <lou...@hp...> - 2007-03-09 12:59:47
|
Hi Lee, salut Bruno,
Le vendredi 09 mars 2007 =C3=A0 06:41 -0500, Lee Mayes a =C3=A9crit :
> Hi Bruno,
>=20
> My comments in-line:
>=20
Mine too :-)
> Bruno Cornec wrote:
> > Hello,
> >
> > It seems that the systemdesigner part of LinuxCOE will be difficult to
> > package.
Not that much. I have a first pass at systemdesigner,
systemdesigner-docs & systemdesigner-rhel done and almost working.
> >
> > 1/ it seems that the planed directory organisation is under a single
> > main dir (I choose /usr/local/systemdesigner) where the LSB/FHS
> > integration would rather imply using /usr, /var/log, /etc, ...
> > We will have to pass a lot of parameters to configure in order to achie=
ve
> > that, I guess.
> > =20
> When we originally decide on filesystem locations, we went with:
>=20
> /opt/package - Static package objects
> /etc/opt/package - Host specific configuration (optional)
> /var/opt/package - Volatile data - namely profiles and logs
>=20
> Bryan and I (mostly Bryan :) parameterized all pathnames with @prefix@=20
> in the code, so it's relatively easy to relocate the package and all its=20
> components to a different path. The /etc tree is completely optional,=20
> but useful as it allows you to protect any changes between updates (it's=20
> a mirror of what's in /opt/package and takes precedence for config/data=20
> directives). I'm happy changing this if it makes sense.
>=20
The directories that we use are set by variables in the .spec file using
the variables that Lee is talking about. So it can be easily changed.
> > 2/ The Apache conf file is not installed by the make install proceudre
> > (under the service dir) and I think it's a bug.
> >
> > =20
> This is a function of 'make integrate', which will also update sudoers=20
> if you require that functionality, which is mostly for older distros=20
> where I need to loopmount initrd to make changes. It's separate from=20
> 'make install' as it's something you only do once.
>=20
The 'make integrate' is done by the RPM that I created. So you can
basically do :
# rpm -vih systemdesigner-4.rpm
# service httpd restart
and access your http://{webserver}/systemdesigner. Voil=C3=A0 !
> > 3/ Is there a bugzilla somewhere we could use ?
> > =20
> There's the standard bug-tracker provided by sf.net:
>=20
> http://sourceforge.net/tracker/?group_id=3D144250&atid=3D758199
>=20
> We should all start using it.
> > 4/ There should also be an easy way to download files compared to CVS
> > (again for some tools helping to build packages it's easier).=20
> > =20
> In the past we've included 'virgin' boot images for the majority of the=20
> distributions we support. While this was convenient for users, it put=20
> us at odds with sourceforge's disk quotes. Chris Slater kindly hosts=20
> 'tarball' snapshots of System Designer at installinux:
>=20
> http://www.instalinux.com/LinuxCOE/snapshot/
>=20
This is the idea behind packaging LinuxCOE both in .debs and .rpm The
work is in progress and you should have at least a working set of RPM by
wednesday night when I leave Grenoble :-)
> We'll be removing these images and including instructions on how to=20
> create your own (and perhaps hosting tarballs of just the images=20
> remotely) to decrease our disk space usage on sf.net and allow true=20
> build releases on sf.net soon.
> > That's all for now, but I may come back with further questions :-)
> > Bruno.
> > =20
> Hope that helps, Bryan will elaborate further I'm sure!
>=20
> Best Regards,
>=20
> Lee
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Linuxcoe-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxcoe-devel
--=20
Louis Bouchard, Linux Support Engineer
EMEA Linux Competency Center,
Linux Ambassador, HP
HP Services 1 Ave du Canada
HP France Z.A. de Courtaboeuf
lou...@hp... 91 947 Les Ulis
http://www.hp.com/go/linux France
http://www.hp.com/fr
|
|
From: Bruno C. <Bru...@hp...> - 2007-03-09 15:13:03
|
Hi Lee, Lee Mayes said on Fri, Mar 09, 2007 at 06:41:40AM -0500: > My comments in-line: As it has to be ;-) > When we originally decide on filesystem locations, we went with: > > /opt/package - Static package objects > /etc/opt/package - Host specific configuration (optional) > /var/opt/package - Volatile data - namely profiles and logs Which is in fact nearer from a lsb type of packaging, rather than an integrated distribution packaging (which uses rather directly /usr, /var, ...) No problem with it, just it makes the configure line of a package longer ;-) > Bryan and I (mostly Bryan :) parameterized all pathnames with @prefix@ > in the code, so it's relatively easy to relocate the package and all its > components to a different path. The /etc tree is completely optional, > but useful as it allows you to protect any changes between updates (it's > a mirror of what's in /opt/package and takes precedence for config/data > directives). I'm happy changing this if it makes sense. I think we will come back with Louis next week on that, after some concrete tests. We will let you know. > >2/ The Apache conf file is not installed by the make install proceudre > >(under the service dir) and I think it's a bug. > > > This is a function of 'make integrate', which will also update sudoers > if you require that functionality, which is mostly for older distros > where I need to loopmount initrd to make changes. It's separate from > 'make install' as it's something you only do once. Grumph, missed that one on the output of the make command sorry. BTW I do not have description of those steps in the Way Station HOWTO. I've now found them (at least partly) in the Admin guide on SF.net. Side question, do you have PDF versions of those 2 guides ? Is the source in a XML|SGML format ? If not do you want I make such a version ? > http://sourceforge.net/tracker/?group_id=144250&atid=758199 > We should all start using it. Ok. Will do as well. > In the past we've included 'virgin' boot images for the majority of the > distributions we support. While this was convenient for users, it put > us at odds with sourceforge's disk quotes. Chris Slater kindly hosts > 'tarball' snapshots of System Designer at installinux: > > http://www.instalinux.com/LinuxCOE/snapshot/ > > We'll be removing these images and including instructions on how to > create your own (and perhaps hosting tarballs of just the images > remotely) to decrease our disk space usage on sf.net and allow true > build releases on sf.net soon. If you want a mirror site, I may also host LinuxCOE content at mondorescue.org, or more precisely at dploy.org ;-) > Hope that helps, Bryan will elaborate further I'm sure! At last next week yes ;-) Best regards, Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org |
|
From: Bruno C. <Bru...@hp...> - 2007-03-09 15:13:42
|
Louis Bouchard said on Fri, Mar 09, 2007 at 01:57:53PM +0100:
> The 'make integrate' is done by the RPM that I created. So you can
> basically do :
>
> # rpm -vih systemdesigner-4.rpm
> # service httpd restart
>
> and access your http://{webserver}/systemdesigner. Voilà !
Great. We will test that next week with you !
> This is the idea behind packaging LinuxCOE both in .debs and .rpm The
> work is in progress and you should have at least a working set of RPM by
> wednesday night when I leave Grenoble :-)
For sure :-) Even more we should have RPMs for all RPMs based distro for
which I already did the job in the past (OpenSuSE, Mandriva, RHEL, SLES,
Fedora). Debian, Gentoo and Slackware could even be looked at ;-)
Bruno.
--
Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET
http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net
Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux
La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org
|
|
From: Bryan G. <Bry...@HP...> - 2007-03-09 16:24:21
|
Bruno, On Fri, Mar 09, 2007 at 04:13:32PM +0100, Bruno Cornec wrote: > > This is the idea behind packaging LinuxCOE both in .debs and .rpm The > > work is in progress and you should have at least a working set of RPM by > > wednesday night when I leave Grenoble :-) > > For sure :-) Even more we should have RPMs for all RPMs based distro for > which I already did the job in the past (OpenSuSE, Mandriva, RHEL, SLES, > Fedora). Debian, Gentoo and Slackware could even be looked at ;-) You can already generate .debs, by following these simple instructions: http://linuxcoe.cvs.sourceforge.net/linuxcoe/packaging/README.deb?revision=1.2&view=markup There are a few things I still need to do to better conform to Debian packaging policy, but this is a good first pass. bryang |
|
From: Bryan G. <Bry...@HP...> - 2007-03-09 16:13:23
|
Bruno, On Fri, Mar 09, 2007 at 11:20:37AM +0100, Bruno Cornec wrote: > Hello, > > It seems that the systemdesigner part of LinuxCOE will be difficult to > package. Actually not, we already have sample debian packaging tools in place and Louis is walking the rpm set. > 1/ it seems that the planed directory organisation is under a single > main dir (I choose /usr/local/systemdesigner) where the LSB/FHS > integration would rather imply using /usr, /var/log, /etc, ... > We will have to pass a lot of parameters to configure in order to achieve > that, I guess. Everything (sans my laziness in /etc@prefix) shorcuts should make it relocatable. Further all the Makefiles have $(DESTIR)@prefix variables to make it even easier to package/relocate. > 2/ The Apache conf file is not installed by the make install proceudre > (under the service dir) and I think it's a bug. make integrate (and done during post install actions for both .deb and .rpm) > 3/ Is there a bugzilla somewhere we could use ? SF site has one. > 4/ There should also be an easy way to download files compared to CVS > (again for some tools helping to build packages it's easier). I just recently updated the tarball snapshots, and the admin guide has the instructions on how to go from CVS->tarball, and will soon have the package make/install instructions as well. bryang |
|
From: Bryan G. <Bry...@HP...> - 2007-03-09 16:22:59
|
Bruno, On Fri, Mar 09, 2007 at 04:11:25PM +0100, Bruno Cornec wrote: > Side question, do you have PDF versions of those 2 guides ? > Is the source in a XML|SGML format ? > If not do you want I make such a version ? FWIW, I have the tools to create this, but don't distribute this by default (since I know you can serve the html file, and can also view it, but can't be so sure of pdf, albeit that is very likely in this day/age). In the docs/guides subdir, you could do: make -f Makefile.transform make -f Makefile.transform html make -f Makefile.transform pdf Only caveat, is that you may have to change the XSLSTYLE parameter to match your system's location of that file. That said, if you think I should distribute the PDF version, I would be happy to include it, moving forward. > > In the past we've included 'virgin' boot images for the majority of the > > distributions we support. While this was convenient for users, it put > > us at odds with sourceforge's disk quotes. Chris Slater kindly hosts > > 'tarball' snapshots of System Designer at installinux: > > > > http://www.instalinux.com/LinuxCOE/snapshot/ > > We'll be removing these images and including instructions on how to > > create your own (and perhaps hosting tarballs of just the images > > remotely) to decrease our disk space usage on sf.net and allow true > > build releases on sf.net soon. > > If you want a mirror site, I may also host LinuxCOE content at > mondorescue.org, or more precisely at dploy.org ;-) That is a great offer as well. And regarding Lee's comments, I am thinking I will make a distinct make dist-images target, to gen such a bootimage only tarball (as a convenience). And, we will either have documentation or a script to help users obtain (and tweak) boot images directly from the desired distribution. > > Hope that helps, Bryan will elaborate further I'm sure! Sorry was home sick all day yesterday, but doing much better today. > At last next week yes ;-) Looking forward to it ! bryang |
|
From: Bruno C. <Bru...@hp...> - 2007-03-19 15:22:37
|
Hello ! Bryan Gartner said on Fri, Mar 09, 2007 at 09:20:10AM -0700: > FWIW, I have the tools to create this, but don't distribute this by > default (since I know you can serve the html file, and can also view > it, but can't be so sure of pdf, albeit that is very likely in this > day/age). In the docs/guides subdir, you could do: > > make -f Makefile.transform Ok. > make -f Makefile.transform html > Only caveat, is that you may have to change the XSLSTYLE parameter to > match your system's location of that file. Doesn't work (no rules to make target). As you said, I had to adapt the docbook.xls location, in order for it to generate something useful. > make -f Makefile.transform pdf OK. But after that ? It created the pdf.in files (which are html files btw) but I don't see what to make from them ? > That said, if you think I should distribute the PDF version, I would be happy > to include it, moving forward. Maybe ;-) Ok, as I do not like to stay on a failure, I used my mondo method which worked without issue for that case : docbook2pdf file.dkb Simple no ;-) I now have the guides I can send to the customer (admin and user guides) Thanks ! Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X