[suggest] Plone CMS

[Nikolay Kim]

Hello,

Plone is open source content management system.
http://plone.org
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 2030 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone-default.spec
Type: text/x-rpm-spec
Size: 3940 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0002.bin

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

Few quick comments:

* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

[Nikolay Kim]

i will make changes and resubmit

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/479ed59e/attachment.bin

[Nikolay Kim]

Hello

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line

fixed

Post by Yury V. Zaytsev
* No %prep section, add everything to sources

fixed

Post by Yury V. Zaytsev
* For Python version detections see SPECs for Python modules

Plone3.3 requires python2.4, it won't work with newer python version

Post by Yury V. Zaytsev
* What is this hardcoded -v 1.4.3 ?

Plone uses zc.buildout building infrastructure
http://pypi.python.org/pypi/zc.buildout/
and this command tells explicitly which version of zc.buildout to use.

Post by Yury V. Zaytsev
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

actually this was core code rpm and default plone server instance rpm.
i will send plone-default spec as separate request.
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 1994 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0001.bin

[Yury V. Zaytsev]

Hi!

It has been a request from our customers because they are used to
installation done inside /opt (VMWare or Adobe all package their RPMs
this way nowadays) If this is an issue on your side let us know and
I'll try to sort this out with our customer asking them if it would be
fine to install the application in /srv for instance.

Not that I really have a *problem* with this, but it's a commonly
respected convention not to install anything that is managed by the
package managing system to /opt as it is meant to be managed outside of
the tree and can be organized very differently from what you might
assume it to be.

On RHEL, the common convention to install the stuff that is exposed to
the web in /var/www or if it's really like an application server or
something along these lines, you install it to /usr (/usr/share/...) and
then create a symlink to /var/www.

See e.g. cacti package for reference.

Probably, /srv would be the most FHS / LSB compatible path, e.g. I use
it to serve git repositories, but as far as I remember, Fedora Packaging
Guidelines explicitly disallow you to rely upon the existence of /srv,
so it's not really an option.

Let us know if you have additional questions.

Well, the most important question for me is whether you are willing to
maintain this package in the future.

I can commit it on your behalf once all the RPMForge specific issues are
cleaned up, but I am not a Plone / Zope expert and I don't personally
use it, nor I have time to maintain it just for the fun of it...

Best,

[Yury V. Zaytsev]

Hi!

It has been a request from our customers because they are used to
installation done inside /opt (VMWare or Adobe all package their RPMs
this way nowadays) If this is an issue on your side let us know and
I'll try to sort this out with our customer asking them if it would be
fine to install the application in /srv for instance.

Not that I really have a *problem* with this, but it's a commonly
respected convention not to install anything that is managed by the
package managing system to /opt as it is meant to be managed outside of
the tree and can be organized very differently from what you might
assume it to be.

On RHEL, the common convention to install the stuff that is exposed to
the web in /var/www or if it's really like an application server or
something along these lines, you install it to /usr (/usr/share/...) and
then create a symlink to /var/www.

See e.g. cacti package for reference.

Probably, /srv would be the most FHS / LSB compatible path, e.g. I use
it to serve git repositories, but as far as I remember, Fedora Packaging
Guidelines explicitly disallow you to rely upon the existence of /srv,
so it's not really an option.

Let us know if you have additional questions.

Well, the most important question for me is whether you are willing to
maintain this package in the future.

I can commit it on your behalf once all the RPMForge specific issues are
cleaned up, but I am not a Plone / Zope expert and I don't personally
use it, nor I have time to maintain it just for the fun of it...

Best,

[Yury V. Zaytsev]

Hi!

It has been a request from our customers because they are used to
installation done inside /opt (VMWare or Adobe all package their RPMs
this way nowadays) If this is an issue on your side let us know and
I'll try to sort this out with our customer asking them if it would be
fine to install the application in /srv for instance.

Not that I really have a *problem* with this, but it's a commonly
respected convention not to install anything that is managed by the
package managing system to /opt as it is meant to be managed outside of
the tree and can be organized very differently from what you might
assume it to be.

On RHEL, the common convention to install the stuff that is exposed to
the web in /var/www or if it's really like an application server or
something along these lines, you install it to /usr (/usr/share/...) and
then create a symlink to /var/www.

See e.g. cacti package for reference.

Probably, /srv would be the most FHS / LSB compatible path, e.g. I use
it to serve git repositories, but as far as I remember, Fedora Packaging
Guidelines explicitly disallow you to rely upon the existence of /srv,
so it's not really an option.

Let us know if you have additional questions.

Well, the most important question for me is whether you are willing to
maintain this package in the future.

I can commit it on your behalf once all the RPMForge specific issues are
cleaned up, but I am not a Plone / Zope expert and I don't personally
use it, nor I have time to maintain it just for the fun of it...

Best,

[Yury V. Zaytsev]

Hi!

It has been a request from our customers because they are used to
installation done inside /opt (VMWare or Adobe all package their RPMs
this way nowadays) If this is an issue on your side let us know and
I'll try to sort this out with our customer asking them if it would be
fine to install the application in /srv for instance.

Not that I really have a *problem* with this, but it's a commonly
respected convention not to install anything that is managed by the
package managing system to /opt as it is meant to be managed outside of
the tree and can be organized very differently from what you might
assume it to be.

On RHEL, the common convention to install the stuff that is exposed to
the web in /var/www or if it's really like an application server or
something along these lines, you install it to /usr (/usr/share/...) and
then create a symlink to /var/www.

See e.g. cacti package for reference.

Probably, /srv would be the most FHS / LSB compatible path, e.g. I use
it to serve git repositories, but as far as I remember, Fedora Packaging
Guidelines explicitly disallow you to rely upon the existence of /srv,
so it's not really an option.

Let us know if you have additional questions.

Well, the most important question for me is whether you are willing to
maintain this package in the future.

I can commit it on your behalf once all the RPMForge specific issues are
cleaned up, but I am not a Plone / Zope expert and I don't personally
use it, nor I have time to maintain it just for the fun of it...

Best,

[Yury V. Zaytsev]

Hi!

It has been a request from our customers because they are used to
installation done inside /opt (VMWare or Adobe all package their RPMs
this way nowadays) If this is an issue on your side let us know and
I'll try to sort this out with our customer asking them if it would be
fine to install the application in /srv for instance.

Not that I really have a *problem* with this, but it's a commonly
respected convention not to install anything that is managed by the
package managing system to /opt as it is meant to be managed outside of
the tree and can be organized very differently from what you might
assume it to be.

On RHEL, the common convention to install the stuff that is exposed to
the web in /var/www or if it's really like an application server or
something along these lines, you install it to /usr (/usr/share/...) and
then create a symlink to /var/www.

See e.g. cacti package for reference.

Probably, /srv would be the most FHS / LSB compatible path, e.g. I use
it to serve git repositories, but as far as I remember, Fedora Packaging
Guidelines explicitly disallow you to rely upon the existence of /srv,
so it's not really an option.

Let us know if you have additional questions.

Well, the most important question for me is whether you are willing to
maintain this package in the future.

I can commit it on your behalf once all the RPMForge specific issues are
cleaned up, but I am not a Plone / Zope expert and I don't personally
use it, nor I have time to maintain it just for the fun of it...

Best,

[Nikolay Kim]

i will make changes and resubmit

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/479ed59e/attachment-0001.bin

[Nikolay Kim]

Hello

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line

fixed

Post by Yury V. Zaytsev
* No %prep section, add everything to sources

fixed

Post by Yury V. Zaytsev
* For Python version detections see SPECs for Python modules

Plone3.3 requires python2.4, it won't work with newer python version

Post by Yury V. Zaytsev
* What is this hardcoded -v 1.4.3 ?

Plone uses zc.buildout building infrastructure
http://pypi.python.org/pypi/zc.buildout/
and this command tells explicitly which version of zc.buildout to use.

Post by Yury V. Zaytsev
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

actually this was core code rpm and default plone server instance rpm.
i will send plone-default spec as separate request.
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 1994 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0003.bin

[Nikolay Kim]

i will make changes and resubmit

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/479ed59e/attachment-0002.bin

[Nikolay Kim]

Hello

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line

fixed

Post by Yury V. Zaytsev
* No %prep section, add everything to sources

fixed

Post by Yury V. Zaytsev
* For Python version detections see SPECs for Python modules

Plone3.3 requires python2.4, it won't work with newer python version

Post by Yury V. Zaytsev
* What is this hardcoded -v 1.4.3 ?

Plone uses zc.buildout building infrastructure
http://pypi.python.org/pypi/zc.buildout/
and this command tells explicitly which version of zc.buildout to use.

Post by Yury V. Zaytsev
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

actually this was core code rpm and default plone server instance rpm.
i will send plone-default spec as separate request.
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 1994 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0004.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0005.bin

[Nikolay Kim]

i will make changes and resubmit

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/479ed59e/attachment-0003.bin

[Nikolay Kim]

Hello

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line

fixed

Post by Yury V. Zaytsev
* No %prep section, add everything to sources

fixed

Post by Yury V. Zaytsev
* For Python version detections see SPECs for Python modules

Plone3.3 requires python2.4, it won't work with newer python version

Post by Yury V. Zaytsev
* What is this hardcoded -v 1.4.3 ?

Plone uses zc.buildout building infrastructure
http://pypi.python.org/pypi/zc.buildout/
and this command tells explicitly which version of zc.buildout to use.

Post by Yury V. Zaytsev
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

actually this was core code rpm and default plone server instance rpm.
i will send plone-default spec as separate request.
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 1994 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0006.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0007.bin

[Nikolay Kim]

i will make changes and resubmit

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100722/479ed59e/attachment-0004.bin>

[Nikolay Kim]

Hello

Post by Yury V. Zaytsev
* Requires/BuildRequires : one per line

fixed

Post by Yury V. Zaytsev
* No %prep section, add everything to sources

fixed

Post by Yury V. Zaytsev
* For Python version detections see SPECs for Python modules

Plone3.3 requires python2.4, it won't work with newer python version

Post by Yury V. Zaytsev
* What is this hardcoded -v 1.4.3 ?

Plone uses zc.buildout building infrastructure
http://pypi.python.org/pypi/zc.buildout/
and this command tells explicitly which version of zc.buildout to use.

Post by Yury V. Zaytsev
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

actually this was core code rpm and default plone server instance rpm.
i will send plone-default spec as separate request.
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 1994 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0008.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100727/a87b8920/attachment-0009.bin>

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

P.S. You might wish to have a look at Trac package.

http://svn.rpmforge.net/svn/trunk/rpms/trac/trac.spec

[Nikolay Kim]

Hello,

Plone is open source content management system.
http://plone.org
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 2030 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0003.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone-default.spec
Type: text/x-rpm-spec
Size: 3940 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0004.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0005.bin

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

Few quick comments:

* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

P.S. You might wish to have a look at Trac package.

http://svn.rpmforge.net/svn/trunk/rpms/trac/trac.spec

[Nikolay Kim]

Hello,

Plone is open source content management system.
http://plone.org
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 2030 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0006.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone-default.spec
Type: text/x-rpm-spec
Size: 3940 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0007.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0008.bin

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

Few quick comments:

* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

P.S. You might wish to have a look at Trac package.

http://svn.rpmforge.net/svn/trunk/rpms/trac/trac.spec

[Nikolay Kim]

Hello,

Plone is open source content management system.
http://plone.org
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 2030 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0009.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone-default.spec
Type: text/x-rpm-spec
Size: 3940 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0010.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
Url : http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0011.bin

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

Few quick comments:

* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

P.S. You might wish to have a look at Trac package.

http://svn.rpmforge.net/svn/trunk/rpms/trac/trac.spec

[Nikolay Kim]

Hello,

Plone is open source content management system.
http://plone.org
--
Nikolay Kim, Enfold Systems
http://www.enfoldsystems.com
Office | [phone] x151 Ext
Fax | [phone]
Skype | fafhrd91
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone.spec
Type: text/x-rpm-spec
Size: 2030 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0012.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plone-default.spec
Type: text/x-rpm-spec
Size: 3940 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0013.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5620 bytes
Desc: not available
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100722/141c204b/attachment-0014.bin>

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

Few quick comments:

* Requires/BuildRequires : one per line
* No %prep section, add everything to sources
* For Python version detections see SPECs for Python modules
* What is this hardcoded -v 1.4.3 ?
* Why installing to /opt? /var/www or /srv???
* Why two SPECs? (I have no clue how it works...)

[Yury V. Zaytsev]

Post by Nikolay Kim
Hello,
Plone is open source content management system.
http://plone.org

P.S. You might wish to have a look at Trac package.

http://svn.rpmforge.net/svn/trunk/rpms/trac/trac.spec

[Pavel Kankovsky]

Perhaps someone (who wants to have it) can make the package relocatable
to make it possible to customize its filesystem layout.

[Pavel Kankovsky]

Perhaps someone (who wants to have it) can make the package relocatable
to make it possible to customize its filesystem layout.

[Pavel Kankovsky]

Perhaps someone (who wants to have it) can make the package relocatable
to make it possible to customize its filesystem layout.

[Pavel Kankovsky]

Perhaps someone (who wants to have it) can make the package relocatable
to make it possible to customize its filesystem layout.

[Pavel Kankovsky]

Perhaps someone (who wants to have it) can make the package relocatable
to make it possible to customize its filesystem layout.