[jira] Created: (MOJO-1308) Support for softlinks

Support for softlinks
---------------------

                 Key: MOJO-1308
                 URL: http://jira.codehaus.org/browse/MOJO-1308
             Project: Mojo
          Issue Type: New Feature
          Components: rpm
            Reporter: Are Gravbrøt
            Priority: Minor


In many cases it is necessary to add softlinks in the rpm complete software installation.

Today that can be accomplished by adding scripts containing ln -s statements.

However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
This leads to creating files that are not reported by rpm -ql.

To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.

Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>

The spec file can be updated in the following way:

%install
ln -s /somesource $RPM_BUILD/sometarget

%files
/sometarget




--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180482#action_180482 ]

Brett Okken commented on MOJO-1308:
-----------------------------------

What if we just added a new attribute to Source called softlinkDestination?

                        <mapping>
                            <directory>/usr/myapp/bin</directory>
                            <directoryIncluded>false</directoryIncluded>
                            <username>root</username>
                            <groupname>root</groupname>
                            <filemode>555</filemode>
                            <sources>
                                <source>
                                    <location>src/main/bin/httpd</location>
                                    <softlinkDestination>/etc/init.d</softlinkDestination>
                                </source>
                            </sources>
                        </mapping>


Then, under %install, we softlink from softlink destination to every file identified by the source.
I believe that the %files info would already be present.

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180482#action_180482 ]

Brett Okken edited comment on MOJO-1308 at 6/16/09 11:24 AM:
-------------------------------------------------------------

What if we just added a new attribute to Source called softlinkDestination?

                        <mapping>
                            <directory>/usr/myapp/bin</directory>
                            <directoryIncluded>false</directoryIncluded>
                            <username>root</username>
                            <groupname>root</groupname>
                            <filemode>555</filemode>
                            <sources>
                                <source>
                                    <location>src/main/bin/httpd</location>
                                    <softlinkDestination>/etc/init.d</softlinkDestination>
                                </source>
                            </sources>
                        </mapping>


Then, under %install, we softlink from softlink destination to every file identified by the source.

      was (Author: kantiger):
    What if we just added a new attribute to Source called softlinkDestination?

                        <mapping>
                            <directory>/usr/myapp/bin</directory>
                            <directoryIncluded>false</directoryIncluded>
                            <username>root</username>
                            <groupname>root</groupname>
                            <filemode>555</filemode>
                            <sources>
                                <source>
                                    <location>src/main/bin/httpd</location>
                                    <softlinkDestination>/etc/init.d</softlinkDestination>
                                </source>
                            </sources>
                        </mapping>


Then, under %install, we softlink from softlink destination to every file identified by the source.
I believe that the %files info would already be present.
 

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180630#action_180630 ]

Are Gravbrøt commented on MOJO-1308:
------------------------------------

Its a good idea. However, for my purpose I would actually need the softlink to be named with a different name than the file. Could that be accomplished by this model?

Thus, I would like to have:

softlinkname -> filename

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180711#action_180711 ]

Brett Okken commented on MOJO-1308:
-----------------------------------

After some more thought, I do not think my suggestion will work.

Whereas you were suggesting a softlinkmapping, how about a softlinkSource which could be used in any regular mapping?

By default, it would link to the same file name, but the <destination> tag could be used to link to a different file name.

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180711#action_180711 ]

Brett Okken edited comment on MOJO-1308 at 6/17/09 2:50 PM:
------------------------------------------------------------

After some more thought, I do not think my suggestion will work.

Whereas you were suggesting a softlinkmapping, how about a softlinkSource which could be used in any regular mapping?

By default, it would link to the same file name, but the <destination> tag could be used to link to a different file name.

For example, you could do the following:

                        <mapping>
                            <directory>/etc/init.d</directory>
                            <directoryIncluded>false</directoryIncluded>
                            <username>root</username>
                            <groupname>root</groupname>
                            <filemode>555</filemode>
                            <sources>
                                <source>
                                    <location>src/main/bin/httpd</location>
                                </source>
                                <softlinkSource>
                                    <location>/etc/init.d/httpd</location>
                                    <destination>apache</destination>
                                </softlinkSource>
                            </sources>
                        </mapping>

This will take you have in /src/main/bin/httpd and put that file in /etc/init.d/httpd and link /etc/init.d/apache to /etc/init.d/httpd.

      was (Author: kantiger):
    After some more thought, I do not think my suggestion will work.

Whereas you were suggesting a softlinkmapping, how about a softlinkSource which could be used in any regular mapping?

By default, it would link to the same file name, but the <destination> tag could be used to link to a different file name.
 

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180775#action_180775 ]

Are Gravbrøt commented on MOJO-1308:
------------------------------------

This would indeed work provided that a full path can be provided in the <destination> tag under the <softlinkSource>. Only problem I can think of is that this full path also may contain a directory which may need special properties like filemode etc.. However, I guess you could add this as a separate mapping directive containing an empty directory if this is needed.

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180831#action_180831 ]

Brett Okken commented on MOJO-1308:
-----------------------------------

Help me understand why <destination> would need to be a full path.

<directory> would include the directory you want the link to be in. <location> would be the source of the link. <destination> would allow using a different name for the specific link file.

Unless I am missing something, this should allow you to provide a link to something you are providing in your package and place that link anywhere in the file system.

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180832#action_180832 ]

Are Gravbrøt commented on MOJO-1308:
------------------------------------

Sorry, by second thought this should indeed work just fine as long as <location> can be specified as a full path.

For instance, if you want  /etc/init.d/apache pointing to /opt/someapp/httpd, you could do something like this:

<mapping>
<directory>/opt/someapp</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<source>
<location>src/main/bin/httpd</location>
</source>
</sources>
</mapping>

<mapping>
<directory>/etc/init.d</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<softlinkSource>
<location>/opt/someapp/httpd</location>
<destination>apache</destination>
</softlinkSource>
</sources>
</mapping>

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180832#action_180832 ]

Are Gravbrøt edited comment on MOJO-1308 at 6/18/09 10:21 AM:
--------------------------------------------------------------

Sorry, by second thought this should indeed work just fine

For instance, if you want  /etc/init.d/apache pointing to /opt/someapp/httpd, you could do something like this:

<mapping>
<directory>/opt/someapp</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<source>
<location>src/main/bin/httpd</location>
</source>
</sources>
</mapping>

<mapping>
<directory>/etc/init.d</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<softlinkSource>
<location>/opt/someapp/httpd</location>
<destination>apache</destination>
</softlinkSource>
</sources>
</mapping>

      was (Author: aregr):
    Sorry, by second thought this should indeed work just fine as long as <location> can be specified as a full path.

For instance, if you want  /etc/init.d/apache pointing to /opt/someapp/httpd, you could do something like this:

<mapping>
<directory>/opt/someapp</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<source>
<location>src/main/bin/httpd</location>
</source>
</sources>
</mapping>

<mapping>
<directory>/etc/init.d</directory>
<directoryIncluded>false</directoryIncluded>
<username>root</username>
<groupname>root</groupname>
<filemode>555</filemode>
<sources>
<softlinkSource>
<location>/opt/someapp/httpd</location>
<destination>apache</destination>
</softlinkSource>
</sources>
</mapping>
 

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180833#action_180833 ]

Brett Okken commented on MOJO-1308:
-----------------------------------

Exactly.

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

     [ http://jira.codehaus.org/browse/MOJO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Okken closed MOJO-1308.
-----------------------------

      Assignee: Brett Okken
    Resolution: Fixed

Added in 2.0-beta-3.
Currently available in latest snapshot:
http://snapshots.repository.codehaus.org/org/codehaus/mojo/rpm-maven-plugin/2.0-beta-3-SNAPSHOT/

> Support for softlinks
> ---------------------
>
>                 Key: MOJO-1308
>                 URL: http://jira.codehaus.org/browse/MOJO-1308
>             Project: Mojo
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Assignee: Brett Okken
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

     [ http://jira.codehaus.org/browse/MRPM-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Okken moved MOJO-1308 to MRPM-18:
---------------------------------------

    Component/s:     (was: rpm)
                 rpm
     Complexity:   (was: Intermediate)
            Key: MRPM-18  (was: MOJO-1308)
        Project: Mojo RPM Plugin  (was: Mojo)

> Support for softlinks
> ---------------------
>
>                 Key: MRPM-18
>                 URL: http://jira.codehaus.org/browse/MRPM-18
>             Project: Mojo RPM Plugin
>          Issue Type: New Feature
>          Components: rpm
>            Reporter: Are Gravbrøt
>            Assignee: Brett Okken
>            Priority: Minor
>
> In many cases it is necessary to add softlinks in the rpm complete software installation.
> Today that can be accomplished by adding scripts containing ln -s statements.
> However, there is a significant drawback in doing it this way, since the %files section of the SPEC file is not updated to reflect this.
> This leads to creating files that are not reported by rpm -ql.
> To remedy this, I suggest adding a feature to enable the addition of softlinks in the configuration section.
> Ex. <softlinkmapping><target>/sometarget</target><source>/somesource</source></softlinkmapping>
> The spec file can be updated in the following way:
> %install
> ln -s /somesource $RPM_BUILD/sometarget
> %files
> /sometarget

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email